Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e8a28c8a95507a8ecff4f0678174084ef55b0abec7f5c964abbba55567ef666

Tx prefix hash: bd17e22fcc8a96334510ce3fcf634984842dbcab7164399772d0c72e6e2e74f1
Tx public key: 95285e370ce0e5f3f0ff778634ad6f0c4bc7c5c529b3090884a05a44446aadde
Timestamp: 1764120773 Timestamp [UCT]: 2025-11-26 01:32:53 Age [y:d:h:m:s]: 00:001:06:25:22
Block: 1420211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 908 RingCT/type: yes/0
Extra: 0195285e370ce0e5f3f0ff778634ad6f0c4bc7c5c529b3090884a05a44446aadde021100000006d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac0e896509d34a367e3fdbb6c92e36bd8d8c20276bc5e201b15c3c2de8ec80a6 0.600000000000 1908752 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": 1420221, "vin": [ { "gen": { "height": 1420211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac0e896509d34a367e3fdbb6c92e36bd8d8c20276bc5e201b15c3c2de8ec80a6" } } ], "extra": [ 1, 149, 40, 94, 55, 12, 224, 229, 243, 240, 255, 119, 134, 52, 173, 111, 12, 75, 199, 197, 197, 41, 179, 9, 8, 132, 160, 90, 68, 68, 106, 173, 222, 2, 17, 0, 0, 0, 6, 214, 225, 157, 124, 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