Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46e65b82295139fe0c79b8ca9f77d38618a8defc2577fdb949768e62dc6c561e

Tx prefix hash: 32227b9cfdae6f1d9b01beea1e713208a2efb69d215e9afd0b35523864507df7
Tx public key: f9488a492efdfdabe4c80e735a1c96f71d60eb1f8ecd7183679e6e4fdba0108e
Timestamp: 1731761296 Timestamp [UCT]: 2024-11-16 12:48:16 Age [y:d:h:m:s]: 00:196:05:54:08
Block: 1154980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140111 RingCT/type: yes/0
Extra: 01f9488a492efdfdabe4c80e735a1c96f71d60eb1f8ecd7183679e6e4fdba0108e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63ebf8c8a9a00aa772481f88092f71d540ba806b42b6d0f689233766d8950596 0.600000000000 1640593 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": 1154990, "vin": [ { "gen": { "height": 1154980 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63ebf8c8a9a00aa772481f88092f71d540ba806b42b6d0f689233766d8950596" } } ], "extra": [ 1, 249, 72, 138, 73, 46, 253, 253, 171, 228, 200, 14, 115, 90, 28, 150, 247, 29, 96, 235, 31, 142, 205, 113, 131, 103, 158, 110, 79, 219, 160, 16, 142, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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