Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a40572c4492a2bba965b43ee17c8f79a0b3d7992e5c903669be8fadfb7d57ae

Tx prefix hash: 31b3cb3b4f3533c2584ff5c2273bbea8cb962602190c04b39f26df67e554b45e
Tx public key: 9c437eb0b64d35dd249a62af47537f916babb2c8ef7aaa3ee6a7839a6c99da5b
Timestamp: 1724329092 Timestamp [UCT]: 2024-08-22 12:18:12 Age [y:d:h:m:s]: 00:122:14:02:36
Block: 1093463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87705 RingCT/type: yes/0
Extra: 019c437eb0b64d35dd249a62af47537f916babb2c8ef7aaa3ee6a7839a6c99da5b021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38400cdc24014d7042ce977681ff5388a830b6450a0a02d6c3b86af15fabf4be 0.600000000000 1568412 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": 1093473, "vin": [ { "gen": { "height": 1093463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38400cdc24014d7042ce977681ff5388a830b6450a0a02d6c3b86af15fabf4be" } } ], "extra": [ 1, 156, 67, 126, 176, 182, 77, 53, 221, 36, 154, 98, 175, 71, 83, 127, 145, 107, 171, 178, 200, 239, 122, 170, 62, 230, 167, 131, 154, 108, 153, 218, 91, 2, 17, 0, 0, 0, 5, 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