Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a8e444e8c39904ee701f191889f781dc1c382ad05b668cd0594bd0e25f738b1

Tx prefix hash: 47264e4b6a6fa7383f6ac13c9e81edaa9229171ce711c6679c82da1adedfdd14
Tx public key: 3e7c4aafe2552c75dec0cf319039040353c80677429a4730254e91e8b9ed0b1b
Timestamp: 1755365585 Timestamp [UCT]: 2025-08-16 17:33:05 Age [y:d:h:m:s]: 00:096:04:46:54
Block: 1347955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68574 RingCT/type: yes/0
Extra: 013e7c4aafe2552c75dec0cf319039040353c80677429a4730254e91e8b9ed0b1b021100000003a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b368f80c06ea48f4fbcbb0bef3802fb901b6b83daa1402b87e5e6e088e3c6f6 0.600000000000 1835878 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": 1347965, "vin": [ { "gen": { "height": 1347955 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b368f80c06ea48f4fbcbb0bef3802fb901b6b83daa1402b87e5e6e088e3c6f6" } } ], "extra": [ 1, 62, 124, 74, 175, 226, 85, 44, 117, 222, 192, 207, 49, 144, 57, 4, 3, 83, 200, 6, 119, 66, 154, 71, 48, 37, 78, 145, 232, 185, 237, 11, 27, 2, 17, 0, 0, 0, 3, 161, 29, 186, 152, 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