Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d878f9ca595fa8de715f12092f9fcc97d68370ea66f50856020a6f7923740773

Tx prefix hash: a18729eb72e1254eb0a5018935af5232b963c71fcbb2c4d38657319f1c917fa0
Tx public key: b09cc51654047e7f4dc5a7528a54b78947b5bea7b1dcdb9ad1f434a325fa56b7
Timestamp: 1715885432 Timestamp [UCT]: 2024-05-16 18:50:32 Age [y:d:h:m:s]: 01:017:05:19:15
Block: 1023442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273241 RingCT/type: yes/0
Extra: 01b09cc51654047e7f4dc5a7528a54b78947b5bea7b1dcdb9ad1f434a325fa56b702110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2448ced04d1f14f1ddfceeec292654ed48d9e56a3f164199280a9cf7aa2ea40 0.600000000000 1488421 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": 1023452, "vin": [ { "gen": { "height": 1023442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2448ced04d1f14f1ddfceeec292654ed48d9e56a3f164199280a9cf7aa2ea40" } } ], "extra": [ 1, 176, 156, 197, 22, 84, 4, 126, 127, 77, 197, 167, 82, 138, 84, 183, 137, 71, 181, 190, 167, 177, 220, 219, 154, 209, 244, 52, 163, 37, 250, 86, 183, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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