Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 300841dab23e24f2d7cc10f83b85817dd9f5d1096a4fe3b6daebca3e7cdabe45

Tx prefix hash: fd232436ff3b68e324c2786d0c58f680e0eb2d8163d6bb65cda22ef34e935406
Tx public key: 6016806431f0dd3a943392ef201f437295d73bfd04b4605dc80359ba269ec059
Timestamp: 1745495002 Timestamp [UTC]: 2025-04-24 11:43:22 Age [y:d:h:m:s]: 01:207:10:53:59
Block: 1268412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 412282 RingCT/type: yes/0
Extra: 016016806431f0dd3a943392ef201f437295d73bfd04b4605dc80359ba269ec05902110000000ddbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 00f63e8bee5cbc7ae2b44d0429bcffaae33eaddcaca2a9f424a9f0eda819b62d 0.000600000000 1755641 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": 1268422, "vin": [ { "gen": { "height": 1268412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00f63e8bee5cbc7ae2b44d0429bcffaae33eaddcaca2a9f424a9f0eda819b62d" } } ], "extra": [ 1, 96, 22, 128, 100, 49, 240, 221, 58, 148, 51, 146, 239, 32, 31, 67, 114, 149, 215, 59, 253, 4, 180, 96, 93, 200, 3, 89, 186, 38, 158, 192, 89, 2, 17, 0, 0, 0, 13, 219, 181, 113, 193, 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: