Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 462d84e5a13cf636344bcd7ecccde016717729415fa337b4544b5418bca95a91

Tx prefix hash: 2d9a07eeaf41920c16c2191edb8f276a9d61820444b49a512d3e7a49ca437894
Tx public key: c6828fec9a725d6d4499402f97c1ea0f19811419f24f9b871314975c9c8194b4
Timestamp: 1748408062 Timestamp [UTC]: 2025-05-28 04:54:22 Age [y:d:h:m:s]: 00:347:08:25:26
Block: 1292535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238573 RingCT/type: yes/0
Extra: 01c6828fec9a725d6d4499402f97c1ea0f19811419f24f9b871314975c9c8194b4021100000003523560da000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4f8c2ac643ab142e8b879706c88bb31e0c7943d4a63013ef00010b9b35422a6d 0.000600000000 1780006 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": 1292545, "vin": [ { "gen": { "height": 1292535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f8c2ac643ab142e8b879706c88bb31e0c7943d4a63013ef00010b9b35422a6d" } } ], "extra": [ 1, 198, 130, 143, 236, 154, 114, 93, 109, 68, 153, 64, 47, 151, 193, 234, 15, 25, 129, 20, 25, 242, 79, 155, 135, 19, 20, 151, 92, 156, 129, 148, 180, 2, 17, 0, 0, 0, 3, 82, 53, 96, 218, 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: