Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c40872b7e0276183c70ac3ae2daee51623ae7682abbc0f7ad5ee79df09258e68

Tx prefix hash: 346f48da7b55093752583ce3968e51a13fcb732dd6f61a96ecb71a7e68ed61e0
Tx public key: 6de95f349df2e35d8a59c2bd0797006525bad066ee91af5609131ee288c74e9b
Timestamp: 1727047334 Timestamp [UCT]: 2024-09-22 23:22:14 Age [y:d:h:m:s]: 01:046:14:57:35
Block: 1115984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291717 RingCT/type: yes/0
Extra: 016de95f349df2e35d8a59c2bd0797006525bad066ee91af5609131ee288c74e9b021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3901028befbf2e597eab5b224c399b5782b9855e5e2cba508c61dbf4f8cb48d0 0.600000000000 1596309 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": 1115994, "vin": [ { "gen": { "height": 1115984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3901028befbf2e597eab5b224c399b5782b9855e5e2cba508c61dbf4f8cb48d0" } } ], "extra": [ 1, 109, 233, 95, 52, 157, 242, 227, 93, 138, 89, 194, 189, 7, 151, 0, 101, 37, 186, 208, 102, 238, 145, 175, 86, 9, 19, 30, 226, 136, 199, 78, 155, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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