Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f2832c54438d4776bcddd08745cd288588e6b4c482ad4bef618bf1842ec0bda

Tx prefix hash: 9b60d1f462aec47355d01eb5ce90e8b1ca44b5c50492982a01f675005146f31c
Tx public key: 6da263a2ed3dfdae33bb5e400d08320a35a95a4b75a6e8c3ad91e2c45f47fec3
Timestamp: 1736338344 Timestamp [UCT]: 2025-01-08 12:12:24 Age [y:d:h:m:s]: 00:160:22:37:45
Block: 1192868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114738 RingCT/type: yes/0
Extra: 016da263a2ed3dfdae33bb5e400d08320a35a95a4b75a6e8c3ad91e2c45f47fec30211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6521da60e3c7644fb2da77367ab0793d872ea2169e91a3b73fc959b04bb4128f 0.600000000000 1679425 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": 1192878, "vin": [ { "gen": { "height": 1192868 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6521da60e3c7644fb2da77367ab0793d872ea2169e91a3b73fc959b04bb4128f" } } ], "extra": [ 1, 109, 162, 99, 162, 237, 61, 253, 174, 51, 187, 94, 64, 13, 8, 50, 10, 53, 169, 90, 75, 117, 166, 232, 195, 173, 145, 226, 196, 95, 71, 254, 195, 2, 17, 0, 0, 0, 5, 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