Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95d45b1eae18c75b228d66ccab8a00538523af0b4b3555aa7b2285c2e71fae72

Tx prefix hash: cca4bed9592c2c3293669ed5c2b85d6c59b430c14ff1e80f43195167c2071c56
Tx public key: 92663aef287996560d927a2dec1d6cbeadc53fdcab9614d5e8122a09215c2406
Timestamp: 1740744595 Timestamp [UCT]: 2025-02-28 12:09:55 Age [y:d:h:m:s]: 00:333:22:34:47
Block: 1229065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236348 RingCT/type: yes/0
Extra: 0192663aef287996560d927a2dec1d6cbeadc53fdcab9614d5e8122a09215c24060211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10d5ab7b2ad07d14d7edbad9218c44c2614995827ada07d7b7ea43ae7798c296 0.600000000000 1715948 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": 1229075, "vin": [ { "gen": { "height": 1229065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10d5ab7b2ad07d14d7edbad9218c44c2614995827ada07d7b7ea43ae7798c296" } } ], "extra": [ 1, 146, 102, 58, 239, 40, 121, 150, 86, 13, 146, 122, 45, 236, 29, 108, 190, 173, 197, 63, 220, 171, 150, 20, 213, 232, 18, 42, 9, 33, 92, 36, 6, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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