Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 271d535b30c8a0f4023ab18b258b793bda4f9f78de31839ab58269e96bbdc56d

Tx prefix hash: 51034de357bfebb3561e1a5d69f66a4cf5d3e35fd31528443d24410e83d34c0b
Tx public key: 0ad9793a871e197a5f1f788c32aa63ea41de2a78d9cb9d206ea53839379729bd
Timestamp: 1719383324 Timestamp [UCT]: 2024-06-26 06:28:44 Age [y:d:h:m:s]: 00:288:16:21:09
Block: 1052437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206282 RingCT/type: yes/0
Extra: 010ad9793a871e197a5f1f788c32aa63ea41de2a78d9cb9d206ea53839379729bd0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 716994db58183578f9b677d2459fae53637ddf703fa81597fab196790d569f52 0.600000000000 1522764 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": 1052447, "vin": [ { "gen": { "height": 1052437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "716994db58183578f9b677d2459fae53637ddf703fa81597fab196790d569f52" } } ], "extra": [ 1, 10, 217, 121, 58, 135, 30, 25, 122, 95, 31, 120, 140, 50, 170, 99, 234, 65, 222, 42, 120, 217, 203, 157, 32, 110, 165, 56, 57, 55, 151, 41, 189, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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