Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0030336f8f8517cbe3859f98c61cdda8e97c21513102f42d3d70a28528ff1773

Tx prefix hash: 83d3c7f43ea2d173d746677ef005e2a2083a606be494d74b455795098720e4c2
Tx public key: be4a01a55dde92053951c80f7b715e59254765a3d05638d58f92f7fee563132f
Timestamp: 1729450087 Timestamp [UCT]: 2024-10-20 18:48:07 Age [y:d:h:m:s]: 00:080:13:39:08
Block: 1135877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57594 RingCT/type: yes/0
Extra: 01be4a01a55dde92053951c80f7b715e59254765a3d05638d58f92f7fee563132f0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 694995c7aab4961e9f016c8a499a2c9cd0e7c9ee6a9d1b718f0edc904f7757c3 0.600000000000 1619216 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": 1135887, "vin": [ { "gen": { "height": 1135877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "694995c7aab4961e9f016c8a499a2c9cd0e7c9ee6a9d1b718f0edc904f7757c3" } } ], "extra": [ 1, 190, 74, 1, 165, 93, 222, 146, 5, 57, 81, 200, 15, 123, 113, 94, 89, 37, 71, 101, 163, 208, 86, 56, 213, 143, 146, 247, 254, 229, 99, 19, 47, 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