Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67fba5fe7d2b035f4cc8af81f1ae0fcb820453bf94695761f4e3a70f19919e1e

Tx prefix hash: 8ad2d5f633991b74f3c0ee837b2bb83b58400c75e6cd41971ef7141548611ed4
Tx public key: 4323b95b4a5fe1be6c4b86457734029f2fd83756f59b47676a729f5ad017cd00
Timestamp: 1730241910 Timestamp [UCT]: 2024-10-29 22:45:10 Age [y:d:h:m:s]: 00:179:18:35:14
Block: 1142397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128333 RingCT/type: yes/0
Extra: 014323b95b4a5fe1be6c4b86457734029f2fd83756f59b47676a729f5ad017cd00021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9b8b8f409fd605f4b937644c8e04ce1cce8da1fc5e0217bd3738d06537123dc 0.600000000000 1626250 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": 1142407, "vin": [ { "gen": { "height": 1142397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9b8b8f409fd605f4b937644c8e04ce1cce8da1fc5e0217bd3738d06537123dc" } } ], "extra": [ 1, 67, 35, 185, 91, 74, 95, 225, 190, 108, 75, 134, 69, 119, 52, 2, 159, 47, 216, 55, 86, 245, 155, 71, 103, 106, 114, 159, 90, 208, 23, 205, 0, 2, 17, 0, 0, 0, 2, 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