Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e028b39f8a601e6a1a0e25ee95360ed5647878912ffdfc992de243c375cb06a8

Tx prefix hash: 979de4b86c12d79e0168577f1224e6f9c7da128e289727f65100d6108b74e436
Tx public key: 427f294717d7e51994284a92b1d699636cb6b220b3b52ee0a655e2f4c8c28100
Timestamp: 1721587114 Timestamp [UCT]: 2024-07-21 18:38:34 Age [y:d:h:m:s]: 00:093:20:48:56
Block: 1070696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67226 RingCT/type: yes/0
Extra: 01427f294717d7e51994284a92b1d699636cb6b220b3b52ee0a655e2f4c8c2810002110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbb55a236ce16e30cdef2e6797759f698c99485fab8b415c2baa7e5ac153698d 0.600000000000 1542641 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": 1070706, "vin": [ { "gen": { "height": 1070696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbb55a236ce16e30cdef2e6797759f698c99485fab8b415c2baa7e5ac153698d" } } ], "extra": [ 1, 66, 127, 41, 71, 23, 215, 229, 25, 148, 40, 74, 146, 177, 214, 153, 99, 108, 182, 178, 32, 179, 181, 46, 224, 166, 85, 226, 244, 200, 194, 129, 0, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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