Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24f9e1c0e90f7f5322a0f12888883070155eb93dc5d3901efc256e79590a368f

Tx prefix hash: 1342cd4b3b10ebaf1ceb6eba4d5f0681fd848770fb7e278f429cb8e26620fe9b
Tx public key: a72b2f2885d82d7712227bd0e52675029955736b4dcf318b262f1579eed5fc66
Timestamp: 1696611941 Timestamp [UCT]: 2023-10-06 17:05:41 Age [y:d:h:m:s]: 01:253:11:05:03
Block: 863858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442135 RingCT/type: yes/0
Extra: 01a72b2f2885d82d7712227bd0e52675029955736b4dcf318b262f1579eed5fc660211000000024b8f5122000000000000000000

1 output(s) for total of 0.842713358000 dcy

stealth address amount amount idx
00: 77e72c27792ca4b1c8aeeb131f466a76f8e049b68b0593e237320c93b19f8603 0.842713358000 1318354 of 0

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": 863868, "vin": [ { "gen": { "height": 863858 } } ], "vout": [ { "amount": 842713358, "target": { "key": "77e72c27792ca4b1c8aeeb131f466a76f8e049b68b0593e237320c93b19f8603" } } ], "extra": [ 1, 167, 43, 47, 40, 133, 216, 45, 119, 18, 34, 123, 208, 229, 38, 117, 2, 153, 85, 115, 107, 77, 207, 49, 139, 38, 47, 21, 121, 238, 213, 252, 102, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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