Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8ab775525edfd9de0adf8e87013f3d9f5fc46fae982c9ad26de9d0b17024981

Tx prefix hash: ed329374a8fff489798e07e3e7bce019a98d0b661c6aa9993ebf0fce959f69e8
Tx public key: 3cf1198f55f816b1dd3ecc232d42850b51cd81fe36ec47806782bab9f1a7e90a
Timestamp: 1737783312 Timestamp [UCT]: 2025-01-25 05:35:12 Age [y:d:h:m:s]: 00:143:10:21:19
Block: 1204797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102253 RingCT/type: yes/0
Extra: 013cf1198f55f816b1dd3ecc232d42850b51cd81fe36ec47806782bab9f1a7e90a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1029738c7d1f4d8dd5fea45df6756243abeb8ebd24ae85a2d459a6eda33a209 0.600000000000 1691490 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": 1204807, "vin": [ { "gen": { "height": 1204797 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1029738c7d1f4d8dd5fea45df6756243abeb8ebd24ae85a2d459a6eda33a209" } } ], "extra": [ 1, 60, 241, 25, 143, 85, 248, 22, 177, 221, 62, 204, 35, 45, 66, 133, 11, 81, 205, 129, 254, 54, 236, 71, 128, 103, 130, 186, 185, 241, 167, 233, 10, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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