Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7eadae5855e0c381296f974dd1b48bca30277e32488b006f5971c01e58ed6aa5

Tx prefix hash: 3a2026443a2b1a967b87e4d49951133399a29fbd4ee07b4b72305ea545fc49de
Tx public key: 6bb1b8bc08e764ef4a9c87c67b1b320d62a3ac83194a928035323738ccc7e64b
Timestamp: 1725735521 Timestamp [UCT]: 2024-09-07 18:58:41 Age [y:d:h:m:s]: 00:233:18:45:22
Block: 1105112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166946 RingCT/type: yes/0
Extra: 016bb1b8bc08e764ef4a9c87c67b1b320d62a3ac83194a928035323738ccc7e64b021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5243338798310c2f611fd76a6c86364188e1f2a991a31f2ebb78a87f1a5eefcd 0.600000000000 1582451 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": 1105122, "vin": [ { "gen": { "height": 1105112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5243338798310c2f611fd76a6c86364188e1f2a991a31f2ebb78a87f1a5eefcd" } } ], "extra": [ 1, 107, 177, 184, 188, 8, 231, 100, 239, 74, 156, 135, 198, 123, 27, 50, 13, 98, 163, 172, 131, 25, 74, 146, 128, 53, 50, 55, 56, 204, 199, 230, 75, 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