Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71d633f4c7ae3f02855ce55f515b294ea0e8f6dd1573fbe5ad364bf01c882d26

Tx prefix hash: 65fb7d686771d7ca7c125528cd29e0590676ee305608116bf6cdf8ff4bac1446
Tx public key: 1444941d09b3a8eec33b75dca676a4be0d9af9fd360f336850bf8312ca8ec789
Timestamp: 1684680867 Timestamp [UCT]: 2023-05-21 14:54:27 Age [y:d:h:m:s]: 01:236:05:14:14
Block: 764999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430249 RingCT/type: yes/0
Extra: 011444941d09b3a8eec33b75dca676a4be0d9af9fd360f336850bf8312ca8ec78902110000000475e3f0e9000000000000000000

1 output(s) for total of 1.791599481000 dcy

stealth address amount amount idx
00: 5c19e7fb7a6ff7328dfd9be1a54d4ded4eb178e260bbcad78e0658a0c29db514 1.791599481000 1213964 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": 765009, "vin": [ { "gen": { "height": 764999 } } ], "vout": [ { "amount": 1791599481, "target": { "key": "5c19e7fb7a6ff7328dfd9be1a54d4ded4eb178e260bbcad78e0658a0c29db514" } } ], "extra": [ 1, 20, 68, 148, 29, 9, 179, 168, 238, 195, 59, 117, 220, 166, 118, 164, 190, 13, 154, 249, 253, 54, 15, 51, 104, 80, 191, 131, 18, 202, 142, 199, 137, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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