Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6985f0e86a7d8d7c08aea6389a89b94e00f1c2a58fbe287d304241bd2fff265

Tx prefix hash: fd73d336ba810389a05298ee7de2f3ec750bf07d66414fdf8b6ecc05157f07d1
Tx public key: 50daad9356c179113ac0f1eafd7b11c342dc56207065cf2756bb99b0f8f6f05b
Timestamp: 1743701622 Timestamp [UTC]: 2025-04-03 17:33:42 Age [y:d:h:m:s]: 01:077:16:43:59
Block: 1253555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310208 RingCT/type: yes/0
Extra: 0150daad9356c179113ac0f1eafd7b11c342dc56207065cf2756bb99b0f8f6f05b021100000008a2ed016b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: db424a0007abb91b8dc301e532b81f646475150d8f5f759122a9be0e271f3b4e 0.000600000000 1740636 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": 1253565, "vin": [ { "gen": { "height": 1253555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db424a0007abb91b8dc301e532b81f646475150d8f5f759122a9be0e271f3b4e" } } ], "extra": [ 1, 80, 218, 173, 147, 86, 193, 121, 17, 58, 192, 241, 234, 253, 123, 17, 195, 66, 220, 86, 32, 112, 101, 207, 39, 86, 187, 153, 176, 248, 246, 240, 91, 2, 17, 0, 0, 0, 8, 162, 237, 1, 107, 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: