Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31ae737a10451c5afa1b28364a24a89b70b1d1cf5cf9d784647d54c789739716

Tx prefix hash: b5af9d0c0c7288ce30a880678e46fa087e6456f6296a9ea99c2cfe09ef4b744a
Tx public key: 1cf99b69e3696dfff22778bfdfdb0c5865cd8bb286eee7d26a89149e79fcd150
Timestamp: 1699353913 Timestamp [UCT]: 2023-11-07 10:45:13 Age [y:d:h:m:s]: 01:358:20:17:11
Block: 886392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 515377 RingCT/type: yes/0
Extra: 011cf99b69e3696dfff22778bfdfdb0c5865cd8bb286eee7d26a89149e79fcd15002110000000575e3f0e9000000000000000000

1 output(s) for total of 0.709602846000 dcy

stealth address amount amount idx
00: baa720ba4507b90cf57d0536216c29db8299feadc88caba8dcff3d61fee897ed 0.709602846000 1342207 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": 886402, "vin": [ { "gen": { "height": 886392 } } ], "vout": [ { "amount": 709602846, "target": { "key": "baa720ba4507b90cf57d0536216c29db8299feadc88caba8dcff3d61fee897ed" } } ], "extra": [ 1, 28, 249, 155, 105, 227, 105, 109, 255, 242, 39, 120, 191, 223, 219, 12, 88, 101, 205, 139, 178, 134, 238, 231, 210, 106, 137, 20, 158, 121, 252, 209, 80, 2, 17, 0, 0, 0, 5, 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