Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5e34cc10028ba56e6aa51f23f4829c522b34fe363b13117a598c8506cfbd61b

Tx prefix hash: 44b0ee3afd575521bd2193b7717a40eb8a9b13605695f4d5e133de8c052bfc2b
Tx public key: 576aaa4a3a359bd625e8ab84f33510bfd0e41ed03e11bb50fcbc6dc0312e691e
Timestamp: 1723899391 Timestamp [UCT]: 2024-08-17 12:56:31 Age [y:d:h:m:s]: 00:066:20:34:32
Block: 1089889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47852 RingCT/type: yes/0
Extra: 01576aaa4a3a359bd625e8ab84f33510bfd0e41ed03e11bb50fcbc6dc0312e691e02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 914d0b020988d81ce8e7c9d5253f1ff530a0a9b6e9565726fbdd9394d755d194 0.600000000000 1564512 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": 1089899, "vin": [ { "gen": { "height": 1089889 } } ], "vout": [ { "amount": 600000000, "target": { "key": "914d0b020988d81ce8e7c9d5253f1ff530a0a9b6e9565726fbdd9394d755d194" } } ], "extra": [ 1, 87, 106, 170, 74, 58, 53, 155, 214, 37, 232, 171, 132, 243, 53, 16, 191, 208, 228, 30, 208, 62, 17, 187, 80, 252, 188, 109, 192, 49, 46, 105, 30, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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