Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8210c638e6196918138ed8e21a3a0485ec04d968cfd17d2865e56a66b849bbc

Tx prefix hash: 3462eb21695232a1243867723a966ec8f7c34f4b7a5f7c2b57a815087d17d406
Tx public key: 003c7d4d085be360027e0033057bfb9706fbebbd039f4ad244ea631e675e4904
Timestamp: 1733181819 Timestamp [UCT]: 2024-12-02 23:23:39 Age [y:d:h:m:s]: 00:143:17:05:06
Block: 1166740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102532 RingCT/type: yes/0
Extra: 01003c7d4d085be360027e0033057bfb9706fbebbd039f4ad244ea631e675e49040211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0f7e66081e7d1562108f322d0e37b5e413243f38185fd73d6c4ef576d3b785b 0.600000000000 1652429 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": 1166750, "vin": [ { "gen": { "height": 1166740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0f7e66081e7d1562108f322d0e37b5e413243f38185fd73d6c4ef576d3b785b" } } ], "extra": [ 1, 0, 60, 125, 77, 8, 91, 227, 96, 2, 126, 0, 51, 5, 123, 251, 151, 6, 251, 235, 189, 3, 159, 74, 210, 68, 234, 99, 30, 103, 94, 73, 4, 2, 17, 0, 0, 0, 7, 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