Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e515245e2025540f4ff85aeef56f4e0993f7b89aa101dd8b5c78cf2a45818079

Tx prefix hash: d10fbfcb20db2ec19f9e4e0b7702bb689434913aace1a3453c103f5848b85797
Tx public key: 7e64981c1c7dd89d74e52b22cada1b86c3bfa5b56c6e784611b8ed8259e921bf
Timestamp: 1761300595 Timestamp [UCT]: 2025-10-24 10:09:55 Age [y:d:h:m:s]: 00:016:11:54:32
Block: 1396851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11806 RingCT/type: yes/0
Extra: 017e64981c1c7dd89d74e52b22cada1b86c3bfa5b56c6e784611b8ed8259e921bf021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12322014a7d39a41e7b45842df4dc654c091bc9ee4c55ecaeca3a1c726448717 0.600000000000 1885138 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": 1396861, "vin": [ { "gen": { "height": 1396851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12322014a7d39a41e7b45842df4dc654c091bc9ee4c55ecaeca3a1c726448717" } } ], "extra": [ 1, 126, 100, 152, 28, 28, 125, 216, 157, 116, 229, 43, 34, 202, 218, 27, 134, 195, 191, 165, 181, 108, 110, 120, 70, 17, 184, 237, 130, 89, 233, 33, 191, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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