Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5da0ac17bec9f3f05e50efecf440c0db99e284b69523e1363c33529019b7f57

Tx prefix hash: 5e6c0cb08637aab8d6b553ad2350aafa6cbfbe7df437aced908cd719ce551b77
Tx public key: 92620d74d849f9c613c92edb6d92fc6c657ac7e6df6cb5fc0dacf27e0514f7ca
Timestamp: 1741185158 Timestamp [UCT]: 2025-03-05 14:32:38 Age [y:d:h:m:s]: 00:258:23:39:56
Block: 1232738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182833 RingCT/type: yes/0
Extra: 0192620d74d849f9c613c92edb6d92fc6c657ac7e6df6cb5fc0dacf27e0514f7ca0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee81e6dedcf4f87f55761a816f160f140a1520d0f5294bc3248f988fbcc52213 0.600000000000 1719651 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": 1232748, "vin": [ { "gen": { "height": 1232738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee81e6dedcf4f87f55761a816f160f140a1520d0f5294bc3248f988fbcc52213" } } ], "extra": [ 1, 146, 98, 13, 116, 216, 73, 249, 198, 19, 201, 46, 219, 109, 146, 252, 108, 101, 122, 199, 230, 223, 108, 181, 252, 13, 172, 242, 126, 5, 20, 247, 202, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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