Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c57579d60dd4899344bb311bd9d2f3ad79e43cf6795d5b3a961c205dedf3727

Tx prefix hash: 596a16b76ae4be326f18dee31d34fd8baed753b600be0a0a5abd5d215b0e549c
Tx public key: 65b8529fd316bdfda7232e2334ea6ae50d1bfc53dd7ec01819bed7d8b39fccf8
Timestamp: 1728678365 Timestamp [UCT]: 2024-10-11 20:26:05 Age [y:d:h:m:s]: 01:088:23:17:01
Block: 1129505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322046 RingCT/type: yes/0
Extra: 0165b8529fd316bdfda7232e2334ea6ae50d1bfc53dd7ec01819bed7d8b39fccf8021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7368d865362074733dd95809fa21157b38d2d7543ae977d803db04ef96f22c1 0.600000000000 1612332 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": 1129515, "vin": [ { "gen": { "height": 1129505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7368d865362074733dd95809fa21157b38d2d7543ae977d803db04ef96f22c1" } } ], "extra": [ 1, 101, 184, 82, 159, 211, 22, 189, 253, 167, 35, 46, 35, 52, 234, 106, 229, 13, 27, 252, 83, 221, 126, 192, 24, 25, 190, 215, 216, 179, 159, 204, 248, 2, 17, 0, 0, 0, 3, 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