Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 2d0dedbb0c8d017663f665af239583dff773ced0e47f3056d291a44b723233e9

Tx prefix hash: 3c46e98e773f78a31b7d1b45b5bdcb80100b9018c1d3803c7e1c91cb043f73a6
Tx public key: 34d84bebec8d01b702bb671cfad4930911d07424eb7150a1efcd91cd30c9e2bb
Timestamp: 1741012247 Timestamp [UCT]: 2025-03-03 14:30:47 Age [y:d:h:m:s]: 00:263:09:50:48
Block: 1231295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186009 RingCT/type: yes/0
Extra: 0134d84bebec8d01b702bb671cfad4930911d07424eb7150a1efcd91cd30c9e2bb0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ea360dfb21db7e5ddc1f0034e0bae245a3483fe1bd12a9187ea31a17548b2a2 0.600000000000 1718202 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1231305, "vin": [ { "gen": { "height": 1231295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ea360dfb21db7e5ddc1f0034e0bae245a3483fe1bd12a9187ea31a17548b2a2" } } ], "extra": [ 1, 52, 216, 75, 235, 236, 141, 1, 183, 2, 187, 103, 28, 250, 212, 147, 9, 17, 208, 116, 36, 235, 113, 80, 161, 239, 205, 145, 205, 48, 201, 226, 187, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8