Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12d501e19fb41ebcaf86e58f5ad60935622fc9bb0c4cba9b6fb1ae8063b8b14c

Tx prefix hash: de64755f4aaf7f23f6d1c1ea9e2042f72c91b0417b42bffbf3e9ea3bc7921785
Tx public key: 9f34bd4be5b3d733c143d35c5c6e342db0bdbd839f0662b3ed6700fce28b6714
Timestamp: 1758394564 Timestamp [UCT]: 2025-09-20 18:56:04 Age [y:d:h:m:s]: 00:131:07:42:55
Block: 1372758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93855 RingCT/type: yes/0
Extra: 019f34bd4be5b3d733c143d35c5c6e342db0bdbd839f0662b3ed6700fce28b671402110000000dad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11c8e2447b3b5e75dbe513d20fc57d81e7be936aa4ed535b33bbb9ae1a013841 0.600000000000 1860843 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": 1372768, "vin": [ { "gen": { "height": 1372758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11c8e2447b3b5e75dbe513d20fc57d81e7be936aa4ed535b33bbb9ae1a013841" } } ], "extra": [ 1, 159, 52, 189, 75, 229, 179, 215, 51, 193, 67, 211, 92, 92, 110, 52, 45, 176, 189, 189, 131, 159, 6, 98, 179, 237, 103, 0, 252, 226, 139, 103, 20, 2, 17, 0, 0, 0, 13, 173, 121, 72, 208, 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