Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dd16c0d6aa36bc192aac37b85ba1befb19684c4a72f72eb4eed8ed396c35824

Tx prefix hash: d3c1ff6684d5784af71076649eacb54a77ce862f8d9e40e6a38a15a15e5a73cf
Tx public key: 6b4b866ef62f7ef7be68609a8645037b2cff38ce674b1ef1821b7dc8a339b760
Timestamp: 1736015450 Timestamp [UCT]: 2025-01-04 18:30:50 Age [y:d:h:m:s]: 00:165:22:10:06
Block: 1190197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118291 RingCT/type: yes/0
Extra: 016b4b866ef62f7ef7be68609a8645037b2cff38ce674b1ef1821b7dc8a339b7600211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de2aed44011ae8719ac009d925c5855f0fb4b6100f783d7af0e8a0f043900fab 0.600000000000 1676712 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": 1190207, "vin": [ { "gen": { "height": 1190197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de2aed44011ae8719ac009d925c5855f0fb4b6100f783d7af0e8a0f043900fab" } } ], "extra": [ 1, 107, 75, 134, 110, 246, 47, 126, 247, 190, 104, 96, 154, 134, 69, 3, 123, 44, 255, 56, 206, 103, 75, 30, 241, 130, 27, 125, 200, 163, 57, 183, 96, 2, 17, 0, 0, 0, 9, 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