Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 060017a861658b4a6f365461e9db2efbd9a48d0810a9d806d9fbb6f927d0a391

Tx prefix hash: 159c0c3b0e6727648a9f59d189fd6ecb7e95b1e79cd630733a88ffd629424df0
Tx public key: 84b67b49e2756632861d1effdbb5f091cca0c405e9e248a5e33948589e49f396
Timestamp: 1751120443 Timestamp [UCT]: 2025-06-28 14:20:43 Age [y:d:h:m:s]: 00:146:09:02:14
Block: 1314581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102692 RingCT/type: yes/0
Extra: 0184b67b49e2756632861d1effdbb5f091cca0c405e9e248a5e33948589e49f39602110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e967944fdb87226f9d62c65cbfe12033b69c651e1811e4f70d8d0dbeb3364fe8 0.600000000000 1802230 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": 1314591, "vin": [ { "gen": { "height": 1314581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e967944fdb87226f9d62c65cbfe12033b69c651e1811e4f70d8d0dbeb3364fe8" } } ], "extra": [ 1, 132, 182, 123, 73, 226, 117, 102, 50, 134, 29, 30, 255, 219, 181, 240, 145, 204, 160, 196, 5, 233, 226, 72, 165, 227, 57, 72, 88, 158, 73, 243, 150, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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