Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: def10e9c8e17678cd632194e5134c53b443a5e81c689e045b890648e44e9eb24

Tx prefix hash: 8af188b9fe75bd891d03c6d09c049342962d628183495c4b28c8e8f6b7909e81
Tx public key: 20938e297d5ee849c28484c56b892759fbced7e5b6d36f13f77fd94a46856330
Timestamp: 1701462574 Timestamp [UCT]: 2023-12-01 20:29:34 Age [y:d:h:m:s]: 01:175:15:52:31
Block: 903864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386750 RingCT/type: yes/0
Extra: 0120938e297d5ee849c28484c56b892759fbced7e5b6d36f13f77fd94a4685633002110000000375e3f0e9000000000000000000

1 output(s) for total of 0.621045378000 dcy

stealth address amount amount idx
00: 3801352f24ac4a169aa0491c3db6e1a0de11c2bb8545016815ebd0c0fc8aba3a 0.621045378000 1360559 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": 903874, "vin": [ { "gen": { "height": 903864 } } ], "vout": [ { "amount": 621045378, "target": { "key": "3801352f24ac4a169aa0491c3db6e1a0de11c2bb8545016815ebd0c0fc8aba3a" } } ], "extra": [ 1, 32, 147, 142, 41, 125, 94, 232, 73, 194, 132, 132, 197, 107, 137, 39, 89, 251, 206, 215, 229, 182, 211, 111, 19, 247, 127, 217, 74, 70, 133, 99, 48, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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