Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3a10126f0e00ee039bc551c3707b9e7e99c4c55c2bc54062b7a3205d75c144a

Tx prefix hash: e6730fadbbf7a87e479411bb2108c4dcf0c109c280317dcbe534df9f0e916bda
Tx public key: 5238028d4064b964cea3aa55a967dc6e52da36c9af724fe2adfcab54bf9ef718
Timestamp: 1750555216 Timestamp [UCT]: 2025-06-22 01:20:16 Age [y:d:h:m:s]: 00:224:09:27:53
Block: 1310123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158151 RingCT/type: yes/0
Extra: 015238028d4064b964cea3aa55a967dc6e52da36c9af724fe2adfcab54bf9ef71802110000000643846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cff961d2bba9ad356e89cf39aac1ce27769b8c6488f6fc7935d952b9e0c0cf3d 0.600000000000 1797740 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": 1310133, "vin": [ { "gen": { "height": 1310123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cff961d2bba9ad356e89cf39aac1ce27769b8c6488f6fc7935d952b9e0c0cf3d" } } ], "extra": [ 1, 82, 56, 2, 141, 64, 100, 185, 100, 206, 163, 170, 85, 169, 103, 220, 110, 82, 218, 54, 201, 175, 114, 79, 226, 173, 252, 171, 84, 191, 158, 247, 24, 2, 17, 0, 0, 0, 6, 67, 132, 109, 102, 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