Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7313ef9d66bd45702cc41acf121d04e34a31fc1ef34728ae19b1a94bc93aab8e

Tx prefix hash: 9d6d0fba942a9ce49dec9c246c83673464d2e4b6a0030eabf679336a45161552
Tx public key: 0efecfeb28df5a59cdb2384681e0b5cce684e4ef58b2ec59c4aff4d2f9ecaa60
Timestamp: 1718209426 Timestamp [UCT]: 2024-06-12 16:23:46 Age [y:d:h:m:s]: 01:209:20:19:59
Block: 1042711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408628 RingCT/type: yes/0
Extra: 010efecfeb28df5a59cdb2384681e0b5cce684e4ef58b2ec59c4aff4d2f9ecaa600211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5bbc8b5bd353ff29bc5c19a32def9538bbfb8603539e3ebb4055c56fa9e1c81 0.600000000000 1511694 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": 1042721, "vin": [ { "gen": { "height": 1042711 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5bbc8b5bd353ff29bc5c19a32def9538bbfb8603539e3ebb4055c56fa9e1c81" } } ], "extra": [ 1, 14, 254, 207, 235, 40, 223, 90, 89, 205, 178, 56, 70, 129, 224, 181, 204, 230, 132, 228, 239, 88, 178, 236, 89, 196, 175, 244, 210, 249, 236, 170, 96, 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