Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 579ad884fcb78dd7325f0aa43c1027278a0bd55df166cdd8854b68dc41eebec7

Tx prefix hash: 03a6c10f93c7ded8753f221a474fe9c60ea15126632519a513568337bd84bda8
Tx public key: aac7688b3ade4e9404752c40c7ffbee12e9a28b1f11d47438e11d69e68a3d6c6
Timestamp: 1659129297 Timestamp [UCT]: 2022-07-29 21:14:57 Age [y:d:h:m:s]: 02:210:14:40:56
Block: 554516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 671684 RingCT/type: yes/0
Extra: 01aac7688b3ade4e9404752c40c7ffbee12e9a28b1f11d47438e11d69e68a3d6c602110000001b6570b1ef000000000000000000

1 output(s) for total of 8.926031746000 dcy

stealth address amount amount idx
00: b8746935fec1edafb1f90eebe67058cda963bdc44ea150892c339e08142e724d 8.926031746000 986372 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": 554526, "vin": [ { "gen": { "height": 554516 } } ], "vout": [ { "amount": 8926031746, "target": { "key": "b8746935fec1edafb1f90eebe67058cda963bdc44ea150892c339e08142e724d" } } ], "extra": [ 1, 170, 199, 104, 139, 58, 222, 78, 148, 4, 117, 44, 64, 199, 255, 190, 225, 46, 154, 40, 177, 241, 29, 71, 67, 142, 17, 214, 158, 104, 163, 214, 198, 2, 17, 0, 0, 0, 27, 101, 112, 177, 239, 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