Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d145204df3e13ce637646f1c8867c607f7170602e8999fb2f78657db5906b5e

Tx prefix hash: dc7b08dc93494dbd8f7103e1999e09c5ca33c4e7ecd69a19ad2e711c770437ec
Tx public key: a6d93c619d55743c3981b277746326fbd85a798af5e9f72c84aada79fd3c80d4
Timestamp: 1716584608 Timestamp [UCT]: 2024-05-24 21:03:28 Age [y:d:h:m:s]: 00:305:10:51:51
Block: 1029239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218294 RingCT/type: yes/0
Extra: 01a6d93c619d55743c3981b277746326fbd85a798af5e9f72c84aada79fd3c80d40211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e719480fa1f9754b752f7cf9e47f9e8f3a945e6c388f05689ac8a32cdc4602d7 0.600000000000 1497274 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": 1029249, "vin": [ { "gen": { "height": 1029239 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e719480fa1f9754b752f7cf9e47f9e8f3a945e6c388f05689ac8a32cdc4602d7" } } ], "extra": [ 1, 166, 217, 60, 97, 157, 85, 116, 60, 57, 129, 178, 119, 116, 99, 38, 251, 216, 90, 121, 138, 245, 233, 247, 44, 132, 170, 218, 121, 253, 60, 128, 212, 2, 17, 0, 0, 0, 2, 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