Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e4b9a43653da38b0f83e61691fc96fc348407b7721842f0787a971aa7fdf2a1

Tx prefix hash: 7d5a9996f4cd35c11ffea94424bdc294f44d64eff33f97e6daa4f7c3fff765a2
Tx public key: fd9848aca1efb769e8bc4fa8985b35da94bbb0595fed732d85b9217a7e8505de
Timestamp: 1685510450 Timestamp [UCT]: 2023-05-31 05:20:50 Age [y:d:h:m:s]: 01:334:12:09:55
Block: 771878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 500286 RingCT/type: yes/0
Extra: 01fd9848aca1efb769e8bc4fa8985b35da94bbb0595fed732d85b9217a7e8505de02110000000175e3f0e9000000000000000000

1 output(s) for total of 1.699996140000 dcy

stealth address amount amount idx
00: 54a9305179fbbaa2c1b9a78674b066d76484ee8ddea644dd07567611f74b4395 1.699996140000 1221259 of 0

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": 771888, "vin": [ { "gen": { "height": 771878 } } ], "vout": [ { "amount": 1699996140, "target": { "key": "54a9305179fbbaa2c1b9a78674b066d76484ee8ddea644dd07567611f74b4395" } } ], "extra": [ 1, 253, 152, 72, 172, 161, 239, 183, 105, 232, 188, 79, 168, 152, 91, 53, 218, 148, 187, 176, 89, 95, 237, 115, 45, 133, 185, 33, 122, 126, 133, 5, 222, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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