Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 011a61dcf5774b106b07156b69301a7372ee79a82c414ea508da58abd0af3c12

Tx prefix hash: e97b5bc4aeeaea196aff19a3c2e4e124a36506746e9be2e05142fb4b7a98fd1b
Tx public key: 2902949423fb2b24c0a0b0867697e6606801d431a250062c1041b42e7401a2cf
Timestamp: 1674132628 Timestamp [UCT]: 2023-01-19 12:50:28 Age [y:d:h:m:s]: 02:147:18:22:34
Block: 678155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 627221 RingCT/type: yes/0
Extra: 012902949423fb2b24c0a0b0867697e6606801d431a250062c1041b42e7401a2cf02110000000752542ceb000000000000000000

1 output(s) for total of 3.475288912000 dcy

stealth address amount amount idx
00: 08b36ab566e5e312f8c78055fd7b8ff693a08c7d33007dd6ef953ce2aaecc4dc 3.475288912000 1119990 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": 678165, "vin": [ { "gen": { "height": 678155 } } ], "vout": [ { "amount": 3475288912, "target": { "key": "08b36ab566e5e312f8c78055fd7b8ff693a08c7d33007dd6ef953ce2aaecc4dc" } } ], "extra": [ 1, 41, 2, 148, 148, 35, 251, 43, 36, 192, 160, 176, 134, 118, 151, 230, 96, 104, 1, 212, 49, 162, 80, 6, 44, 16, 65, 180, 46, 116, 1, 162, 207, 2, 17, 0, 0, 0, 7, 82, 84, 44, 235, 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