Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47496cf520d7791357c69e6171e612d1f911b8a5c4830fdc0d71c4a8e3f6d7a9

Tx prefix hash: b8b2492c536d22c6d027727e9be71118feb9bcce5b8d1bf581d8d7def7453821
Tx public key: a72497f33c60db9a39f0cb3ae9513ddf94d8ee77d0870d7860b983f8c730b201
Timestamp: 1761161184 Timestamp [UTC]: 2025-10-22 19:26:24 Age [y:d:h:m:s]: 01:026:16:59:59
Block: 1395692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285435 RingCT/type: yes/0
Extra: 01a72497f33c60db9a39f0cb3ae9513ddf94d8ee77d0870d7860b983f8c730b201021100000002e4dc9009000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 92d6ca087ff24564dcddc6fb9190b7268b8718342304687a58445e36dc2b266a 0.000600000000 1883975 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": 1395702, "vin": [ { "gen": { "height": 1395692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92d6ca087ff24564dcddc6fb9190b7268b8718342304687a58445e36dc2b266a" } } ], "extra": [ 1, 167, 36, 151, 243, 60, 96, 219, 154, 57, 240, 203, 58, 233, 81, 61, 223, 148, 216, 238, 119, 208, 135, 13, 120, 96, 185, 131, 248, 199, 48, 178, 1, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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: