Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55d9e21b399fa1e1d9caf8dbad617811fdf8f147c1cca98265ac27c8a674993e

Tx prefix hash: 928b496f7fb517904d15d8cc4fa349b0136323c99cd0d5e9d8ea42f0afd0b4e8
Tx public key: 7054022190b3dd7e70832a4a4dc6e8146804ceead769cfa29d17e4fd1827250e
Timestamp: 1744608609 Timestamp [UTC]: 2025-04-14 05:30:09 Age [y:d:h:m:s]: 01:219:10:31:02
Block: 1261083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420913 RingCT/type: yes/0
Extra: 017054022190b3dd7e70832a4a4dc6e8146804ceead769cfa29d17e4fd1827250e0211000000028368266d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0160c6e020d7e3c7d944c32840864de4b795313e22b76b67050be325d5ca0e78 0.000600000000 1748248 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": 1261093, "vin": [ { "gen": { "height": 1261083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0160c6e020d7e3c7d944c32840864de4b795313e22b76b67050be325d5ca0e78" } } ], "extra": [ 1, 112, 84, 2, 33, 144, 179, 221, 126, 112, 131, 42, 74, 77, 198, 232, 20, 104, 4, 206, 234, 215, 105, 207, 162, 157, 23, 228, 253, 24, 39, 37, 14, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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: