Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a86a264a7f5f09b774659cc4fd9c2aa0c223f93a1b53e37101dbe1f0e108b536

Tx prefix hash: 514f72adeb17f7b3568e38afb66214f6bfe8f72289e230129832566460d4f824
Tx public key: 1c70fd9df5b8ced285439404501cf128cebef768abf6f9cede983ff0e69d6eb4
Timestamp: 1689949912 Timestamp [UCT]: 2023-07-21 14:31:52 Age [y:d:h:m:s]: 02:111:08:07:36
Block: 808690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 599259 RingCT/type: yes/0
Extra: 011c70fd9df5b8ced285439404501cf128cebef768abf6f9cede983ff0e69d6eb402110000000833af99f4000000000000000000

1 output(s) for total of 1.283732227000 dcy

stealth address amount amount idx
00: e8048e7aa20f4d8533328d9538c6cefccd697d945ef18c4c5993fef22baa737a 1.283732227000 1260283 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": 808700, "vin": [ { "gen": { "height": 808690 } } ], "vout": [ { "amount": 1283732227, "target": { "key": "e8048e7aa20f4d8533328d9538c6cefccd697d945ef18c4c5993fef22baa737a" } } ], "extra": [ 1, 28, 112, 253, 157, 245, 184, 206, 210, 133, 67, 148, 4, 80, 28, 241, 40, 206, 190, 247, 104, 171, 246, 249, 206, 222, 152, 63, 240, 230, 157, 110, 180, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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