Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fddfb1fdb0c094d4112bdf9f851ee0540f83cbc86b1e12129f41c0d8eca1067

Tx prefix hash: b9b6c7f79bd5aa39d2c76b6132140d790a9deb4d17d8d503350d601123d469cf
Tx public key: 6ff0936d2b3854015ab3abd0a286b6057976fc7f0f204005a36d53273cb7f615
Timestamp: 1747765173 Timestamp [UTC]: 2025-05-20 18:19:33 Age [y:d:h:m:s]: 01:183:00:07:34
Block: 1287205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394862 RingCT/type: yes/0
Extra: 016ff0936d2b3854015ab3abd0a286b6057976fc7f0f204005a36d53273cb7f6150211000000031f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fe1be3e8c99632f7f32dbc80d4de9c8314fba3e82528e5c9b8dfc73c8c543488 0.000600000000 1774672 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": 1287215, "vin": [ { "gen": { "height": 1287205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe1be3e8c99632f7f32dbc80d4de9c8314fba3e82528e5c9b8dfc73c8c543488" } } ], "extra": [ 1, 111, 240, 147, 109, 43, 56, 84, 1, 90, 179, 171, 208, 162, 134, 182, 5, 121, 118, 252, 127, 15, 32, 64, 5, 163, 109, 83, 39, 60, 183, 246, 21, 2, 17, 0, 0, 0, 3, 31, 144, 81, 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: