Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed08226c710f0998c705ac1c00f5fed49ef60ee8ae54f0e857342c20b3c660ec

Tx prefix hash: 11d04133f330106a6407e524e18f3a727a320f78cf08cb28b30edea9c086cd48
Tx public key: 10444b34df4f3c29bad9ddea60a4dc95dfebfe3fbbe21af9ee556c814124bff2
Timestamp: 1743870140 Timestamp [UCT]: 2025-04-05 16:22:20 Age [y:d:h:m:s]: 00:236:04:43:40
Block: 1254958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166559 RingCT/type: yes/0
Extra: 0110444b34df4f3c29bad9ddea60a4dc95dfebfe3fbbe21af9ee556c814124bff202110000000c6c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a00009c72680d62a3e00c5bf1c24675a0e71cb8e64e2d3f5d731f393e5cdc733 0.600000000000 1742055 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": 1254968, "vin": [ { "gen": { "height": 1254958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a00009c72680d62a3e00c5bf1c24675a0e71cb8e64e2d3f5d731f393e5cdc733" } } ], "extra": [ 1, 16, 68, 75, 52, 223, 79, 60, 41, 186, 217, 221, 234, 96, 164, 220, 149, 223, 235, 254, 63, 187, 226, 26, 249, 238, 85, 108, 129, 65, 36, 191, 242, 2, 17, 0, 0, 0, 12, 108, 152, 170, 61, 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