Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60162e216973da35ce798896878478c884cb4eb2cb46931a05f360e09283c48c

Tx prefix hash: a1fc745a8823d57184d4d390ad9f1ea06a5db87b01b01d66df51281c197ecb53
Tx public key: 53262306c7004cb407f4cc75e2fa6aa0f98c481047c845bbd2d817030a1100b5
Timestamp: 1710100712 Timestamp [UCT]: 2024-03-10 19:58:32 Age [y:d:h:m:s]: 01:080:20:36:46
Block: 975499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318817 RingCT/type: yes/0
Extra: 0153262306c7004cb407f4cc75e2fa6aa0f98c481047c845bbd2d817030a1100b5021100000003b757f2ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2496aaec129793e58270ebd1e8afa1f8332e955b4aeecd94385bf44dec6344ee 0.600000000000 1435472 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": 975509, "vin": [ { "gen": { "height": 975499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2496aaec129793e58270ebd1e8afa1f8332e955b4aeecd94385bf44dec6344ee" } } ], "extra": [ 1, 83, 38, 35, 6, 199, 0, 76, 180, 7, 244, 204, 117, 226, 250, 106, 160, 249, 140, 72, 16, 71, 200, 69, 187, 210, 216, 23, 3, 10, 17, 0, 181, 2, 17, 0, 0, 0, 3, 183, 87, 242, 172, 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