Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f59b78323c039160157fad394d30e77bc86c98f1d3ecc23f47d851cc3a69efd6

Tx prefix hash: f213f373549e5f8d9cd83ece5850f9702427bb091bb433b4b0d3a840f2924716
Tx public key: e5b1ff3d8ef950da56de73b9b61a1af62947bed0c40e137fe69bd591b2976dfe
Timestamp: 1756116849 Timestamp [UCT]: 2025-08-25 10:14:09 Age [y:d:h:m:s]: 00:118:16:29:25
Block: 1354064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84799 RingCT/type: yes/0
Extra: 01e5b1ff3d8ef950da56de73b9b61a1af62947bed0c40e137fe69bd591b2976dfe0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0ba8f5f8bc4ef85335aae4b877d3e48bdaecbba26bc8e6c093cce45217ad6d4 0.600000000000 1842045 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": 1354074, "vin": [ { "gen": { "height": 1354064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0ba8f5f8bc4ef85335aae4b877d3e48bdaecbba26bc8e6c093cce45217ad6d4" } } ], "extra": [ 1, 229, 177, 255, 61, 142, 249, 80, 218, 86, 222, 115, 185, 182, 26, 26, 246, 41, 71, 190, 208, 196, 14, 19, 127, 230, 155, 213, 145, 178, 151, 109, 254, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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