Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9118d48feedcf944c10547382d9750764cadd39d5d2e6679757fa4bb261ec29

Tx prefix hash: 86503c0284f17406999ea54a535f4707a1dd2f39227f3f77c2c62679cd0cab93
Tx public key: af1b5649e5b8d10276fade8e671aeeb599f37246e1c209c33ce4942671f29c77
Timestamp: 1723633365 Timestamp [UCT]: 2024-08-14 11:02:45 Age [y:d:h:m:s]: 01:087:02:37:22
Block: 1087681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320717 RingCT/type: yes/0
Extra: 01af1b5649e5b8d10276fade8e671aeeb599f37246e1c209c33ce4942671f29c77021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85cafd8758a698f934be7f8cb0935fbeb17ab896ae82e56d88c6d7e65a8e12b2 0.600000000000 1562292 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": 1087691, "vin": [ { "gen": { "height": 1087681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85cafd8758a698f934be7f8cb0935fbeb17ab896ae82e56d88c6d7e65a8e12b2" } } ], "extra": [ 1, 175, 27, 86, 73, 229, 184, 209, 2, 118, 250, 222, 142, 103, 26, 238, 181, 153, 243, 114, 70, 225, 194, 9, 195, 60, 228, 148, 38, 113, 242, 156, 119, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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