Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4c4b195d23bdf384538f53f84ad72fdf5e861ab6a3e269a2e24f2b5e2c4e7b1

Tx prefix hash: 6440436eb2cc8861ede31351d663c435c51a684078bcf61897ba7745ca588598
Tx public key: 96025777b39d21dcbbde8be3a8781866f152f6f1da232d231e1ea8e47f269564
Timestamp: 1718057562 Timestamp [UCT]: 2024-06-10 22:12:42 Age [y:d:h:m:s]: 00:142:09:10:39
Block: 1041458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101908 RingCT/type: yes/0
Extra: 0196025777b39d21dcbbde8be3a8781866f152f6f1da232d231e1ea8e47f26956402110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c59e638676a10e2bb8941aa0d6e22848ad67df470cca117df3f7e4bf1fcb7629 0.600000000000 1510135 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": 1041468, "vin": [ { "gen": { "height": 1041458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c59e638676a10e2bb8941aa0d6e22848ad67df470cca117df3f7e4bf1fcb7629" } } ], "extra": [ 1, 150, 2, 87, 119, 179, 157, 33, 220, 187, 222, 139, 227, 168, 120, 24, 102, 241, 82, 246, 241, 218, 35, 45, 35, 30, 30, 168, 228, 127, 38, 149, 100, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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