Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b62068f168c2272038e04415ef03c9291d0d3f8c1eeb234e1e1ce8de5e396f0

Tx prefix hash: bf8a26a900474bc9e4305ee9040b43d57101d1073ecac7e0ebefa93555b9c510
Tx public key: 75b234cfa564c41fb3f3baaf41b98931103e5f44d9d7f4582518989e753459a5
Timestamp: 1703182009 Timestamp [UCT]: 2023-12-21 18:06:49 Age [y:d:h:m:s]: 01:099:14:03:42
Block: 918123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332291 RingCT/type: yes/0
Extra: 0175b234cfa564c41fb3f3baaf41b98931103e5f44d9d7f4582518989e753459a50211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63b0eb5ea34e09b782218303a27eab66ac24dc5ecee440fb5a46b0a3335a1d02 0.600000000000 1375761 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": 918133, "vin": [ { "gen": { "height": 918123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63b0eb5ea34e09b782218303a27eab66ac24dc5ecee440fb5a46b0a3335a1d02" } } ], "extra": [ 1, 117, 178, 52, 207, 165, 100, 196, 31, 179, 243, 186, 175, 65, 185, 137, 49, 16, 62, 95, 68, 217, 215, 244, 88, 37, 24, 152, 158, 117, 52, 89, 165, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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