Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ddf14e05c30fa5e7b1172be9e91e8d153bc277d739fa334079552e0d2923c86

Tx prefix hash: b8c1e79ad1c8818ef5c1fd70b24cc8bd42d458d0e64662c3147286e9371c5886
Tx public key: b961b97d03dc70c301e85cb46a221a892a768bead94f22b052c9052027a7ccd8
Timestamp: 1720957623 Timestamp [UCT]: 2024-07-14 11:47:03 Age [y:d:h:m:s]: 00:258:20:27:49
Block: 1065506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184910 RingCT/type: yes/0
Extra: 01b961b97d03dc70c301e85cb46a221a892a768bead94f22b052c9052027a7ccd802110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e913777ab13624130d91762f0ca841813a134c6b657f5c8b97c552482f43f252 0.600000000000 1536053 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": 1065516, "vin": [ { "gen": { "height": 1065506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e913777ab13624130d91762f0ca841813a134c6b657f5c8b97c552482f43f252" } } ], "extra": [ 1, 185, 97, 185, 125, 3, 220, 112, 195, 1, 232, 92, 180, 106, 34, 26, 137, 42, 118, 139, 234, 217, 79, 34, 176, 82, 201, 5, 32, 39, 167, 204, 216, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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