Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 146ee38fed4ca0fc398c2bd35e66e494e9fde69e2fb7c8d1800859fff45df1ca

Tx prefix hash: a61795930bae1513052f3dc42eca0d7aeaa198556641a8a4ae3db90cc6644159
Tx public key: 3c05cdfe3f8fc933859c9eaba38650224c4a3ea9874cdc85b5f61409e4af41d2
Timestamp: 1648499549 Timestamp [UCT]: 2022-03-28 20:32:29 Age [y:d:h:m:s]: 02:244:07:06:26
Block: 468439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 694123 RingCT/type: yes/0
Extra: 013c05cdfe3f8fc933859c9eaba38650224c4a3ea9874cdc85b5f61409e4af41d202110000000506faf294000000000000000000

1 output(s) for total of 17.213428759000 dcy

stealth address amount amount idx
00: 413dcb3bef9895f603f73168ced87670ff0f04e799190c3965501fb8f740a313 17.213428759000 887159 of 0

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": 468449, "vin": [ { "gen": { "height": 468439 } } ], "vout": [ { "amount": 17213428759, "target": { "key": "413dcb3bef9895f603f73168ced87670ff0f04e799190c3965501fb8f740a313" } } ], "extra": [ 1, 60, 5, 205, 254, 63, 143, 201, 51, 133, 156, 158, 171, 163, 134, 80, 34, 76, 74, 62, 169, 135, 76, 220, 133, 181, 246, 20, 9, 228, 175, 65, 210, 2, 17, 0, 0, 0, 5, 6, 250, 242, 148, 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