Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cc670ab5575b9ec848a36e3ce4b256e3bf23fee49ec4c6ce06b1285ed631a96

Tx prefix hash: 4c9c150b399bf6cc52fd88d2df44f18efeff215157793790b98841eb06a21faf
Tx public key: 424a028c5fd4330e9076a83bdd6b2ce1fac39b99b41cd03f342d3f9526f3838e
Timestamp: 1724231856 Timestamp [UCT]: 2024-08-21 09:17:36 Age [y:d:h:m:s]: 00:232:13:07:28
Block: 1092652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166059 RingCT/type: yes/0
Extra: 01424a028c5fd4330e9076a83bdd6b2ce1fac39b99b41cd03f342d3f9526f3838e021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cfb2c1948a350334aa087baf8937291e8da36524e87d9361a31eb1d3dfd80b52 0.600000000000 1567441 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": 1092662, "vin": [ { "gen": { "height": 1092652 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cfb2c1948a350334aa087baf8937291e8da36524e87d9361a31eb1d3dfd80b52" } } ], "extra": [ 1, 66, 74, 2, 140, 95, 212, 51, 14, 144, 118, 168, 59, 221, 107, 44, 225, 250, 195, 155, 153, 180, 28, 208, 63, 52, 45, 63, 149, 38, 243, 131, 142, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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