Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 893b2e965caa412823bcfc5939a319b6788d639f03eab57fc0dec993c6ee3dce

Tx prefix hash: 88ca55f070d2a550f7d5c6c3b3aec7e21cb45cc599be9af6083ababd98a9c45b
Tx public key: d5ee72c664a2f27efbb3346a7df1a65cecef11b27c67277ecb7c58975a01d1c3
Timestamp: 1721043736 Timestamp [UCT]: 2024-07-15 11:42:16 Age [y:d:h:m:s]: 00:256:12:27:41
Block: 1066225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183246 RingCT/type: yes/0
Extra: 01d5ee72c664a2f27efbb3346a7df1a65cecef11b27c67277ecb7c58975a01d1c3021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0999eac682c2c7d94a13ce13b3e128d11035e60a865817771668d1667a07365c 0.600000000000 1536798 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": 1066235, "vin": [ { "gen": { "height": 1066225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0999eac682c2c7d94a13ce13b3e128d11035e60a865817771668d1667a07365c" } } ], "extra": [ 1, 213, 238, 114, 198, 100, 162, 242, 126, 251, 179, 52, 106, 125, 241, 166, 92, 236, 239, 17, 178, 124, 103, 39, 126, 203, 124, 88, 151, 90, 1, 209, 195, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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