Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a77bb6b0f18df753944d833c5914317487ad4cc05ab4b100ef0e1bfdc4c81a1

Tx prefix hash: b2ff3f416256201ef493cae0f3093cfccc69fabfc8b57caa6a4200489b78d1af
Tx public key: c6c2cc4bc42dd6d781a3cc69b566f1236b9fdbd8954a738036b0f637cd7734f9
Timestamp: 1754812208 Timestamp [UCT]: 2025-08-10 07:50:08 Age [y:d:h:m:s]: 00:095:23:54:57
Block: 1344002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67807 RingCT/type: yes/0
Extra: 01c6c2cc4bc42dd6d781a3cc69b566f1236b9fdbd8954a738036b0f637cd7734f902110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fecb63d99b1de89a5302deb335623343deb7fc99c4492f61e0dcae19327148ca 0.600000000000 1831847 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": 1344012, "vin": [ { "gen": { "height": 1344002 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fecb63d99b1de89a5302deb335623343deb7fc99c4492f61e0dcae19327148ca" } } ], "extra": [ 1, 198, 194, 204, 75, 196, 45, 214, 215, 129, 163, 204, 105, 181, 102, 241, 35, 107, 159, 219, 216, 149, 74, 115, 128, 54, 176, 246, 55, 205, 119, 52, 249, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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