Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f40c3e1c6a4e42b81df57d10209158bbeb45d58b06cb0a47e8add5fdbe8126fc

Tx prefix hash: b6ea2f38dc724601272db04dac74d141c1279b418eff35c74d4dc9f0b3926c69
Tx public key: 9fffee400d7aee7bc1d2e5592ec39fe90f50432015ac47bd616f90a7798a3c5f
Timestamp: 1772839108 Timestamp [UTC]: 2026-03-06 23:18:28 Age [y:d:h:m:s]: 00:257:23:00:49
Block: 1492251 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189953 RingCT/type: yes/0
Extra: 019fffee400d7aee7bc1d2e5592ec39fe90f50432015ac47bd616f90a7798a3c5f021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8e71fd8894e3f49f30bc2cee5e92ce0da70ebc7df673073a7621032dabf57ad9 0.000600000000 1981791 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": 1492261, "vin": [ { "gen": { "height": 1492251 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e71fd8894e3f49f30bc2cee5e92ce0da70ebc7df673073a7621032dabf57ad9" } } ], "extra": [ 1, 159, 255, 238, 64, 13, 122, 238, 123, 193, 210, 229, 89, 46, 195, 159, 233, 15, 80, 67, 32, 21, 172, 71, 189, 97, 111, 144, 167, 121, 138, 60, 95, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 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: