Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8533b913629a0289d68d81eae045107d0085193dc1ae0c8e50907691aedc990a

Tx prefix hash: 4ed1b6272473df35445d18cc274d28cd9d5c0f99f020d7bf595954fc41587bde
Tx public key: acb8fc0519b66dd5d02ba56810d8bdd93d2f46bfc26977543f2ba3cf75333c22
Timestamp: 1581217447 Timestamp [UCT]: 2020-02-09 03:04:07 Age [y:d:h:m:s]: 04:291:15:44:49
Block: 61002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1100590 RingCT/type: yes/0
Extra: 01acb8fc0519b66dd5d02ba56810d8bdd93d2f46bfc26977543f2ba3cf75333c22021100000006d81c26c0000000000000000000

1 output(s) for total of 385.368194013000 dcy

stealth address amount amount idx
00: 13dc5671a5a246120b8c9c424a7b6e3aca5746dad8d704eba18ca1750a97acad 385.368194013000 112453 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": 61012, "vin": [ { "gen": { "height": 61002 } } ], "vout": [ { "amount": 385368194013, "target": { "key": "13dc5671a5a246120b8c9c424a7b6e3aca5746dad8d704eba18ca1750a97acad" } } ], "extra": [ 1, 172, 184, 252, 5, 25, 182, 109, 213, 208, 43, 165, 104, 16, 216, 189, 217, 61, 47, 70, 191, 194, 105, 119, 84, 63, 43, 163, 207, 117, 51, 60, 34, 2, 17, 0, 0, 0, 6, 216, 28, 38, 192, 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