Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30a9e8755915563bc34fa515903ed1dfafbc3ced8a0f759784d19c468019ba76

Tx prefix hash: 546eb7d9a26e955f962a0eefe6a2f50817e53896aecb8858d440354456aa379e
Tx public key: 10860f4b1f39cd8666211f2bd8bf6f774626dc6d05afed55bab7aeaa0a9f2122
Timestamp: 1756141926 Timestamp [UCT]: 2025-08-25 17:12:06 Age [y:d:h:m:s]: 00:157:09:22:26
Block: 1354270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112341 RingCT/type: yes/0
Extra: 0110860f4b1f39cd8666211f2bd8bf6f774626dc6d05afed55bab7aeaa0a9f2122021100000003ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59fa1861c1cb82fa0df46a410c73cf176aea0dc94a6d179164b47badde3bcf26 0.600000000000 1842257 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": 1354280, "vin": [ { "gen": { "height": 1354270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59fa1861c1cb82fa0df46a410c73cf176aea0dc94a6d179164b47badde3bcf26" } } ], "extra": [ 1, 16, 134, 15, 75, 31, 57, 205, 134, 102, 33, 31, 43, 216, 191, 111, 119, 70, 38, 220, 109, 5, 175, 237, 85, 186, 183, 174, 170, 10, 159, 33, 34, 2, 17, 0, 0, 0, 3, 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