Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cdc5e9eb1b0213db3b59eec6f8e9ddc9f6328fc861ef0c9c925cca08d914712

Tx prefix hash: f0505367fcebd8d941ef6cb819fd97e4d76feb81b08a424f4b4dce16d1944d55
Tx public key: aada5d824537614b2ed8c1380255ebeef4fb68e4366e59c966e9c5bcf9ae7f54
Timestamp: 1688704510 Timestamp [UCT]: 2023-07-07 04:35:10 Age [y:d:h:m:s]: 01:237:21:45:14
Block: 798369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431115 RingCT/type: yes/0
Extra: 01aada5d824537614b2ed8c1380255ebeef4fb68e4366e59c966e9c5bcf9ae7f5402110000000475e3f0e9000000000000000000

1 output(s) for total of 1.388903961000 dcy

stealth address amount amount idx
00: 3c2c8520914258d5d7c67c8e7e42d5a0defc6ae612d51d631f0ea193cf0f5373 1.388903961000 1249302 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": 798379, "vin": [ { "gen": { "height": 798369 } } ], "vout": [ { "amount": 1388903961, "target": { "key": "3c2c8520914258d5d7c67c8e7e42d5a0defc6ae612d51d631f0ea193cf0f5373" } } ], "extra": [ 1, 170, 218, 93, 130, 69, 55, 97, 75, 46, 216, 193, 56, 2, 85, 235, 238, 244, 251, 104, 228, 54, 110, 89, 201, 102, 233, 197, 188, 249, 174, 127, 84, 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