Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a0ba04b947907b43de32a12d152deca1250c8da57dafbb5480fc887054ed1a9

Tx prefix hash: f561498283a03d3f531bccf9bd654635c729deabed23b25fe941d38c3c616b32
Tx public key: 915c805a294a7ee9e19812abc569d90cf9121a3d8caf6865ee3c40b46436b3c4
Timestamp: 1698640626 Timestamp [UCT]: 2023-10-30 04:37:06 Age [y:d:h:m:s]: 01:177:07:00:02
Block: 880692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387717 RingCT/type: yes/0
Extra: 01915c805a294a7ee9e19812abc569d90cf9121a3d8caf6865ee3c40b46436b3c402110000000233af99f4000000000000000000

1 output(s) for total of 0.741142679000 dcy

stealth address amount amount idx
00: 5cb613a16d7619901b2a0f8732e891f9c44843ece5d66dc720a18f659aef10aa 0.741142679000 1336258 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": 880702, "vin": [ { "gen": { "height": 880692 } } ], "vout": [ { "amount": 741142679, "target": { "key": "5cb613a16d7619901b2a0f8732e891f9c44843ece5d66dc720a18f659aef10aa" } } ], "extra": [ 1, 145, 92, 128, 90, 41, 74, 126, 233, 225, 152, 18, 171, 197, 105, 217, 12, 249, 18, 26, 61, 140, 175, 104, 101, 238, 60, 64, 180, 100, 54, 179, 196, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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