Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d5eacef82c28a1712949ba2e654ace93e23caa2a00dd762227fe9faa9931de3

Tx prefix hash: 150645ae4ec93b3a95b2e4102d48746cd4b727ff62870dd9c6ad56b68dbdce45
Tx public key: 74d99030a88c39b9f994b916fd36b7f3749206c3854c4b0d926d4e8d93c0b2ab
Timestamp: 1578273822 Timestamp [UCT]: 2020-01-06 01:23:42 Age [y:d:h:m:s]: 04:362:05:13:24
Block: 39526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1148164 RingCT/type: yes/0
Extra: 0174d99030a88c39b9f994b916fd36b7f3749206c3854c4b0d926d4e8d93c0b2ab02110000000217786bcf000000000000000000

1 output(s) for total of 453.993654841000 dcy

stealth address amount amount idx
00: 6631ac98d0c9d9f77eb92ec9f411f6667d40f9266e0343e2bcd9b2f0a5eb3866 453.993654841000 68338 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": 39536, "vin": [ { "gen": { "height": 39526 } } ], "vout": [ { "amount": 453993654841, "target": { "key": "6631ac98d0c9d9f77eb92ec9f411f6667d40f9266e0343e2bcd9b2f0a5eb3866" } } ], "extra": [ 1, 116, 217, 144, 48, 168, 140, 57, 185, 249, 148, 185, 22, 253, 54, 183, 243, 116, 146, 6, 195, 133, 76, 75, 13, 146, 109, 78, 141, 147, 192, 178, 171, 2, 17, 0, 0, 0, 2, 23, 120, 107, 207, 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