Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f27f1528784eda2f30837d399be2a4369e9a718c35425e00bfd60b8a909d13c4

Tx prefix hash: d47355e5ada3b56c3706b4956332124260d3bd59e4cac7d53b71ccb25024e479
Tx public key: bcd91ce902737166c3b13bac5d5e36e5d2b77449ec10dadd9eed856d39c891dc
Timestamp: 1699885410 Timestamp [UCT]: 2023-11-13 14:23:30 Age [y:d:h:m:s]: 01:127:07:52:31
Block: 890798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352199 RingCT/type: yes/0
Extra: 01bcd91ce902737166c3b13bac5d5e36e5d2b77449ec10dadd9eed856d39c891dc021100000007faf35c9c000000000000000000

1 output(s) for total of 0.686145841000 dcy

stealth address amount amount idx
00: fb07d6a8cecb01cad512eba13c838940f611ea9369294d369de3521298015966 0.686145841000 1346829 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": 890808, "vin": [ { "gen": { "height": 890798 } } ], "vout": [ { "amount": 686145841, "target": { "key": "fb07d6a8cecb01cad512eba13c838940f611ea9369294d369de3521298015966" } } ], "extra": [ 1, 188, 217, 28, 233, 2, 115, 113, 102, 195, 177, 59, 172, 93, 94, 54, 229, 210, 183, 116, 73, 236, 16, 218, 221, 158, 237, 133, 109, 57, 200, 145, 220, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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