Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3229a8d3eca5b5fbf0576c8fc97ae4a8c33c84db913a0a057ad7b09b921a4f4

Tx prefix hash: 64a54d43a25b66d2100c90f0e7634ec9f5508baac6a7f74501e8e977d37ae118
Tx public key: e5ecb704dafb3d84ca5c6cd23ee5aa137920e8038befef02029398c7a1861ed4
Timestamp: 1638047910 Timestamp [UCT]: 2021-11-27 21:18:30 Age [y:d:h:m:s]: 03:154:17:19:36
Block: 383495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 889285 RingCT/type: yes/0
Extra: 01e5ecb704dafb3d84ca5c6cd23ee5aa137920e8038befef02029398c7a1861ed4021100000002379224c2000000000000000000

1 output(s) for total of 32.909572763000 dcy

stealth address amount amount idx
00: c166f938a26dab7c2cb98cbcc7b0d876e74daf5adbb58fdaa4a946513083352d 32.909572763000 774232 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": 383505, "vin": [ { "gen": { "height": 383495 } } ], "vout": [ { "amount": 32909572763, "target": { "key": "c166f938a26dab7c2cb98cbcc7b0d876e74daf5adbb58fdaa4a946513083352d" } } ], "extra": [ 1, 229, 236, 183, 4, 218, 251, 61, 132, 202, 92, 108, 210, 62, 229, 170, 19, 121, 32, 232, 3, 139, 239, 239, 2, 2, 147, 152, 199, 161, 134, 30, 212, 2, 17, 0, 0, 0, 2, 55, 146, 36, 194, 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