Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35adf7fc8d156c45a835f03706156796a7073bcabfc8d50690593e3bb7f2d4cd

Tx prefix hash: 63b9094b8c463614f5891ab4f509d5593864c4c607bad9175c599bdaa97cdd2e
Tx public key: e225b3b38d95b90b86ef4582c81f1d0424786355be3091e58c4ec464fd3f8cf3
Timestamp: 1704043489 Timestamp [UCT]: 2023-12-31 17:24:49 Age [y:d:h:m:s]: 01:145:02:12:02
Block: 925263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364844 RingCT/type: yes/0
Extra: 01e225b3b38d95b90b86ef4582c81f1d0424786355be3091e58c4ec464fd3f8cf302110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e94aa7aea354b2d5f6017a876cdaa202c2df56c7a127f6fa2de36dabbd03f92 0.600000000000 1383023 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": 925273, "vin": [ { "gen": { "height": 925263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e94aa7aea354b2d5f6017a876cdaa202c2df56c7a127f6fa2de36dabbd03f92" } } ], "extra": [ 1, 226, 37, 179, 179, 141, 149, 185, 11, 134, 239, 69, 130, 200, 31, 29, 4, 36, 120, 99, 85, 190, 48, 145, 229, 140, 78, 196, 100, 253, 63, 140, 243, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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