Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6301fe88c8eab47fcbb33f221b319c8153af3c6198b1ff2549396935aa4e01e6

Tx prefix hash: 0695f7119fa051ff17c4add012765739b8941a04b9c059313da313161dbb9881
Tx public key: 9594c9b140bcfea375b97f2011af9796e7f9d09f2f7c2d063902bc3a28f82a00
Timestamp: 1715592645 Timestamp [UCT]: 2024-05-13 09:30:45 Age [y:d:h:m:s]: 00:227:12:52:52
Block: 1021039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162832 RingCT/type: yes/0
Extra: 019594c9b140bcfea375b97f2011af9796e7f9d09f2f7c2d063902bc3a28f82a0002110000000139e1d5d3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a15b73d6db4d4d97d7db45699598c1afa59fff79b6c78c30a493450b2fdfb2bd 0.600000000000 1485210 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": 1021049, "vin": [ { "gen": { "height": 1021039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a15b73d6db4d4d97d7db45699598c1afa59fff79b6c78c30a493450b2fdfb2bd" } } ], "extra": [ 1, 149, 148, 201, 177, 64, 188, 254, 163, 117, 185, 127, 32, 17, 175, 151, 150, 231, 249, 208, 159, 47, 124, 45, 6, 57, 2, 188, 58, 40, 248, 42, 0, 2, 17, 0, 0, 0, 1, 57, 225, 213, 211, 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