Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 789881bdb5a8c93da28611665c45b47511cefcd101d436f38f2052f4d7d52a6f

Tx prefix hash: e50ce441414a18a7c21a0b68d7d8d698a5bd0e7bd8e4bd03e56083fffe806591
Tx public key: b986b2e0dfde60a178f02cd9b15bbce5ed231a56166eb61be4c839a40cadd470
Timestamp: 1705123660 Timestamp [UCT]: 2024-01-13 05:27:40 Age [y:d:h:m:s]: 00:364:00:54:17
Block: 934206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260645 RingCT/type: yes/0
Extra: 01b986b2e0dfde60a178f02cd9b15bbce5ed231a56166eb61be4c839a40cadd470021100000001ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bceda10793dc89ae9a2767b6f0678cf1f4ba40b6528a876110935697b79a1f38 0.600000000000 1392194 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": 934216, "vin": [ { "gen": { "height": 934206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bceda10793dc89ae9a2767b6f0678cf1f4ba40b6528a876110935697b79a1f38" } } ], "extra": [ 1, 185, 134, 178, 224, 223, 222, 96, 161, 120, 240, 44, 217, 177, 91, 188, 229, 237, 35, 26, 86, 22, 110, 182, 27, 228, 200, 57, 164, 12, 173, 212, 112, 2, 17, 0, 0, 0, 1, 172, 50, 141, 17, 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