Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb3b2c9e4753e9db61b66740717f5f36d08d38e69d37f4f35cac2e8cc4010755

Tx prefix hash: 0037a75723984d8a3e217b6141a1cc644566a0d107eb06f74a86aad6dc49b459
Tx public key: 34a0b3e09f83e79668e65d88c0ff9907f8d31809abb9811b119c2a7490b0d2d3
Timestamp: 1750281351 Timestamp [UTC]: 2025-06-18 21:15:51 Age [y:d:h:m:s]: 01:151:20:24:07
Block: 1307897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372638 RingCT/type: yes/0
Extra: 0134a0b3e09f83e79668e65d88c0ff9907f8d31809abb9811b119c2a7490b0d2d3021100000007d8e7d241000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 361ad2f7f5378aa2c9cfd443b2fd342c8491425be9649ffc5a7bff149f156253 0.000600000000 1795508 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": 1307907, "vin": [ { "gen": { "height": 1307897 } } ], "vout": [ { "amount": 600000000, "target": { "key": "361ad2f7f5378aa2c9cfd443b2fd342c8491425be9649ffc5a7bff149f156253" } } ], "extra": [ 1, 52, 160, 179, 224, 159, 131, 231, 150, 104, 230, 93, 136, 192, 255, 153, 7, 248, 211, 24, 9, 171, 185, 129, 27, 17, 156, 42, 116, 144, 176, 210, 211, 2, 17, 0, 0, 0, 7, 216, 231, 210, 65, 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: