Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68d00aceec7754db62c417ff02267da57ca4cfc363524ea6e6f6ca8d17259057

Tx prefix hash: ecc70be0e7d8ef8404c6689e92ab870b2b4e159a0cc38f741612c6357ac9eb8f
Tx public key: 8ca90e79a47ed9118c0829c939a06b7bcf9718e1db1e3a461d91d3144bd88f6b
Timestamp: 1741393965 Timestamp [UCT]: 2025-03-08 00:32:45 Age [y:d:h:m:s]: 00:257:21:54:35
Block: 1234462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182068 RingCT/type: yes/0
Extra: 018ca90e79a47ed9118c0829c939a06b7bcf9718e1db1e3a461d91d3144bd88f6b0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 763c9e3399899de5b595c03af11f0254c792f1fe299cf2efcac0dfd91c4f1d37 0.600000000000 1721389 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": 1234472, "vin": [ { "gen": { "height": 1234462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "763c9e3399899de5b595c03af11f0254c792f1fe299cf2efcac0dfd91c4f1d37" } } ], "extra": [ 1, 140, 169, 14, 121, 164, 126, 217, 17, 140, 8, 41, 201, 57, 160, 107, 123, 207, 151, 24, 225, 219, 30, 58, 70, 29, 145, 211, 20, 75, 216, 143, 107, 2, 17, 0, 0, 0, 1, 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