Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 354a12857746ca6012dbaa755d309e467e596fb8b42890112b5e8d211e6c2111

Tx prefix hash: 46b32c076c7484a49f8306824f30d91cf243e21d886f09e8a563d5d2e521485d
Tx public key: bf7b9fe9f612531b2b474561abae8458c72473d389275d7d74a6bf553b8c5f6f
Timestamp: 1751534535 Timestamp [UTC]: 2025-07-03 09:22:15 Age [y:d:h:m:s]: 01:138:09:41:34
Block: 1317830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363499 RingCT/type: yes/0
Extra: 01bf7b9fe9f612531b2b474561abae8458c72473d389275d7d74a6bf553b8c5f6f021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ab9651361559a59aa97cd8de60d5a610a962b653d25b499ab6c9ca579c3d8c58 0.000600000000 1805501 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": 1317840, "vin": [ { "gen": { "height": 1317830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab9651361559a59aa97cd8de60d5a610a962b653d25b499ab6c9ca579c3d8c58" } } ], "extra": [ 1, 191, 123, 159, 233, 246, 18, 83, 27, 43, 71, 69, 97, 171, 174, 132, 88, 199, 36, 115, 211, 137, 39, 93, 125, 116, 166, 191, 85, 59, 140, 95, 111, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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: