Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f318918de0092558abdcd9fe626f7e72a2b5dcfdbca0a564065e101ab774bc59

Tx prefix hash: e4df6f854eee0f67e7a880246708719e8814052753e6f26480f476b72c7d4ddd
Tx public key: 475e90657f9a69f302a35d01faad3a6e2c50c1329b24fef629d0b25c6af77d6e
Timestamp: 1762295972 Timestamp [UTC]: 2025-11-04 22:39:32 Age [y:d:h:m:s]: 01:010:23:35:11
Block: 1405084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274114 RingCT/type: yes/0
Extra: 01475e90657f9a69f302a35d01faad3a6e2c50c1329b24fef629d0b25c6af77d6e021100000001df5a247a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bf0e0eb26dea13b2eaf13a91a24574196f706dd3fb2062fe0e28877f6e0c8b62 0.000600000000 1893453 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 dinastycoin-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": 1405094, "vin": [ { "gen": { "height": 1405084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf0e0eb26dea13b2eaf13a91a24574196f706dd3fb2062fe0e28877f6e0c8b62" } } ], "extra": [ 1, 71, 94, 144, 101, 127, 154, 105, 243, 2, 163, 93, 1, 250, 173, 58, 110, 44, 80, 193, 50, 155, 36, 254, 246, 41, 208, 178, 92, 106, 247, 125, 110, 2, 17, 0, 0, 0, 1, 223, 90, 36, 122, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: