Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9b7bef42efb1501807de01ffe8a323713b2b9bbc757820694aed68d9ce1b1e0

Tx prefix hash: 628cd5f5146218e0f497eb1448e5507515b7f6f98b407fdddf519d732f7dc599
Tx public key: 4565825594fc67d1de3714fd0b188ad670954d575c6800b7c2bfac03c9ca56a5
Timestamp: 1725614207 Timestamp [UCT]: 2024-09-06 09:16:47 Age [y:d:h:m:s]: 01:064:16:56:36
Block: 1104107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304666 RingCT/type: yes/0
Extra: 014565825594fc67d1de3714fd0b188ad670954d575c6800b7c2bfac03c9ca56a5021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd623eaffa8dcb68388a6ac141e2384d6ef6e8b4eade55c9cd6eea18482100dc 0.600000000000 1581174 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": 1104117, "vin": [ { "gen": { "height": 1104107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd623eaffa8dcb68388a6ac141e2384d6ef6e8b4eade55c9cd6eea18482100dc" } } ], "extra": [ 1, 69, 101, 130, 85, 148, 252, 103, 209, 222, 55, 20, 253, 11, 24, 138, 214, 112, 149, 77, 87, 92, 104, 0, 183, 194, 191, 172, 3, 201, 202, 86, 165, 2, 17, 0, 0, 0, 7, 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