Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9acce4474f7fdc891a8c9d2b81a629034729a0cc7d6a0bde07555e2a167af9e

Tx prefix hash: e4b4f554de9df7c1c35948ad3abe017da902439d931474b516ff90c0f0cc7260
Tx public key: bbb7a74c0c98aa81db0dd743f854930f52f2f67ff27fdd2533d70e2a5ba5175c
Timestamp: 1713209962 Timestamp [UCT]: 2024-04-15 19:39:22 Age [y:d:h:m:s]: 01:028:08:55:49
Block: 1001245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281260 RingCT/type: yes/0
Extra: 01bbb7a74c0c98aa81db0dd743f854930f52f2f67ff27fdd2533d70e2a5ba5175c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c791cff1013b8ed96c047fdde2761a32236d028e4acc80bfd2d49b26f016267 0.600000000000 1461749 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": 1001255, "vin": [ { "gen": { "height": 1001245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c791cff1013b8ed96c047fdde2761a32236d028e4acc80bfd2d49b26f016267" } } ], "extra": [ 1, 187, 183, 167, 76, 12, 152, 170, 129, 219, 13, 215, 67, 248, 84, 147, 15, 82, 242, 246, 127, 242, 127, 221, 37, 51, 215, 14, 42, 91, 165, 23, 92, 2, 17, 0, 0, 0, 3, 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