Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af12fa3b8713aa9c8b9caf59848e2ed32d7b0a931563f045ff176150b4b78353

Tx prefix hash: 675fe9d51c7bbd52d436f2ac878838873eb0a459a03fb2dc1d11480b2af13e1a
Tx public key: 093215186f255573f9a7e5e11546a7efa057d00359dd05e813de305a669a5051
Timestamp: 1712258638 Timestamp [UCT]: 2024-04-04 19:23:58 Age [y:d:h:m:s]: 01:075:04:57:25
Block: 993364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314642 RingCT/type: yes/0
Extra: 01093215186f255573f9a7e5e11546a7efa057d00359dd05e813de305a669a505102110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d5c501cae2fb8694d3566581251dc82bdf0e74d3a58e3972e7ab963d91e2e0c 0.600000000000 1453750 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": 993374, "vin": [ { "gen": { "height": 993364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d5c501cae2fb8694d3566581251dc82bdf0e74d3a58e3972e7ab963d91e2e0c" } } ], "extra": [ 1, 9, 50, 21, 24, 111, 37, 85, 115, 249, 167, 229, 225, 21, 70, 167, 239, 160, 87, 208, 3, 89, 221, 5, 232, 19, 222, 48, 90, 102, 154, 80, 81, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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