Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 178560ffa04b005b623ee3aa9ef95ed808825965e70aa231fb938099f010c61c

Tx prefix hash: 7a89d28d974a474113a4d7f55f4d8c4641261dd1e465a4d772d6b8df769e8556
Tx public key: e595febb5f386baa882d5888bf790bf2fbabb38bd2dbb627ccd366efa1a80d01
Timestamp: 1705813643 Timestamp [UCT]: 2024-01-21 05:07:23 Age [y:d:h:m:s]: 01:086:17:23:58
Block: 939907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323093 RingCT/type: yes/0
Extra: 01e595febb5f386baa882d5888bf790bf2fbabb38bd2dbb627ccd366efa1a80d010211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49dd7c4f73a27ad0e9566e137879c8b3c1a0e6094a3cabed6bb511cd418e346d 0.600000000000 1398041 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": 939917, "vin": [ { "gen": { "height": 939907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49dd7c4f73a27ad0e9566e137879c8b3c1a0e6094a3cabed6bb511cd418e346d" } } ], "extra": [ 1, 229, 149, 254, 187, 95, 56, 107, 170, 136, 45, 88, 136, 191, 121, 11, 242, 251, 171, 179, 139, 210, 219, 182, 39, 204, 211, 102, 239, 161, 168, 13, 1, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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