Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f1e0523c7e1d712c0a9a837c8d6a24aab6d7fcbffdc9a5c63f3992b0aaf0f35

Tx prefix hash: 3a47b9d6cb0e774c863c5146e433e79de7cc39bf8b32dd81270f0d4ada2c4ae7
Tx public key: 33a7a5dd83035fe40a31d3851141b0cc23f2af2fa515c3d4fbdc7cf2a4bd1a15
Timestamp: 1773583222 Timestamp [UTC]: 2026-03-15 14:00:22 Age [y:d:h:m:s]: 00:057:13:19:14
Block: 1498420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33379 RingCT/type: yes/0
Extra: 0133a7a5dd83035fe40a31d3851141b0cc23f2af2fa515c3d4fbdc7cf2a4bd1a1502110000000bf188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1518974c66e4315f1b18bafec660689a21f46a13596ba2ff7074e9f1933ebf64 0.000600000000 1988066 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": 1498430, "vin": [ { "gen": { "height": 1498420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1518974c66e4315f1b18bafec660689a21f46a13596ba2ff7074e9f1933ebf64" } } ], "extra": [ 1, 51, 167, 165, 221, 131, 3, 95, 228, 10, 49, 211, 133, 17, 65, 176, 204, 35, 242, 175, 47, 165, 21, 195, 212, 251, 220, 124, 242, 164, 189, 26, 21, 2, 17, 0, 0, 0, 11, 241, 136, 200, 168, 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: