Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac87a8d4c2f2e675ab06e75069e6fe012670320d478575c867ae5f7e1e91fc76

Tx prefix hash: 0cd747523d66f91edfc929f6c18aeb1d185f1c1fb95fd3131c84b364f412a4ff
Tx public key: dd87ba3bb9c1f09a946bacd2c6999dc4967d0e39e605d7b4ae43bf3d6394c358
Timestamp: 1742261890 Timestamp [UTC]: 2025-03-18 01:38:10 Age [y:d:h:m:s]: 01:248:04:36:38
Block: 1241659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441558 RingCT/type: yes/0
Extra: 01dd87ba3bb9c1f09a946bacd2c6999dc4967d0e39e605d7b4ae43bf3d6394c358021100000009007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ed157c82d59ad7f15903ccd9f97e02c61322fa7fda80ee99e1ad4468b4a2ae66 0.000600000000 1728632 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": 1241669, "vin": [ { "gen": { "height": 1241659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed157c82d59ad7f15903ccd9f97e02c61322fa7fda80ee99e1ad4468b4a2ae66" } } ], "extra": [ 1, 221, 135, 186, 59, 185, 193, 240, 154, 148, 107, 172, 210, 198, 153, 157, 196, 150, 125, 14, 57, 230, 5, 215, 180, 174, 67, 191, 61, 99, 148, 195, 88, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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: