Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 243fc25da94ebb2c44d13198bd7a3f9c00bec17891e41a94e91948e20bc02b07

Tx prefix hash: dc4c27d9757a01d038e0e25330bdf2868947a9b4ba3f18a1fb674cdd9408c620
Tx public key: aecdbf6d9997ac8b3ce532decffacf9fcbcc1f5d7b6a513c4e3eb0d733a07f8b
Timestamp: 1724838338 Timestamp [UCT]: 2024-08-28 09:45:38 Age [y:d:h:m:s]: 00:237:03:14:51
Block: 1097663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169353 RingCT/type: yes/0
Extra: 01aecdbf6d9997ac8b3ce532decffacf9fcbcc1f5d7b6a513c4e3eb0d733a07f8b021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b00bf2a8aa3c9e0738dd0d8604f693a8f7e3340155fc8d67b9b139f421ceb756 0.600000000000 1573108 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": 1097673, "vin": [ { "gen": { "height": 1097663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b00bf2a8aa3c9e0738dd0d8604f693a8f7e3340155fc8d67b9b139f421ceb756" } } ], "extra": [ 1, 174, 205, 191, 109, 153, 151, 172, 139, 60, 229, 50, 222, 207, 250, 207, 159, 203, 204, 31, 93, 123, 106, 81, 60, 78, 62, 176, 215, 51, 160, 127, 139, 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