Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccb7f4ec92a0576629f0436e6dc63704b92e2ee74e9be71acc01bdc27ae3d8fa

Tx prefix hash: e739644275b1278094550ffadcf21aa1743cd1cd1103937be3964a1a32e5c2e6
Tx public key: cb981f5ec6d0404b789c978e1298e262f2d7871696e28b0c8b2ccacad485024d
Timestamp: 1705925172 Timestamp [UCT]: 2024-01-22 12:06:12 Age [y:d:h:m:s]: 01:074:02:02:23
Block: 940834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314050 RingCT/type: yes/0
Extra: 01cb981f5ec6d0404b789c978e1298e262f2d7871696e28b0c8b2ccacad485024d02110000001359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a62e299c9fdcff88681605367cf430db511c4dfa8421ff52d5ae89d32bfda4b0 0.600000000000 1398974 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": 940844, "vin": [ { "gen": { "height": 940834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a62e299c9fdcff88681605367cf430db511c4dfa8421ff52d5ae89d32bfda4b0" } } ], "extra": [ 1, 203, 152, 31, 94, 198, 208, 64, 75, 120, 156, 151, 142, 18, 152, 226, 98, 242, 215, 135, 22, 150, 226, 139, 12, 139, 44, 202, 202, 212, 133, 2, 77, 2, 17, 0, 0, 0, 19, 89, 218, 211, 245, 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