Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 510bfa1c85930371a4d29a14d523acd8153ed90d1b1b0f8e1ef4e9005fc00023

Tx prefix hash: 40e41d5416cd37f332c35b13501fbc5bf58f91dcbc7ac871730ffd53b16a701e
Tx public key: 8f1d1395d516910925e8b951d406b4c1b1d3aceff2ae0072ec7cc8df24466370
Timestamp: 1737440403 Timestamp [UCT]: 2025-01-21 06:20:03 Age [y:d:h:m:s]: 00:151:13:12:34
Block: 1201950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108009 RingCT/type: yes/0
Extra: 018f1d1395d516910925e8b951d406b4c1b1d3aceff2ae0072ec7cc8df244663700211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f9b9cbb7a5948a1af4665c843599ed83a8695d0826c6b0972e043e34fb821c9 0.600000000000 1688609 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": 1201960, "vin": [ { "gen": { "height": 1201950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f9b9cbb7a5948a1af4665c843599ed83a8695d0826c6b0972e043e34fb821c9" } } ], "extra": [ 1, 143, 29, 19, 149, 213, 22, 145, 9, 37, 232, 185, 81, 212, 6, 180, 193, 177, 211, 172, 239, 242, 174, 0, 114, 236, 124, 200, 223, 36, 70, 99, 112, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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