Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db32e58c22385e5f00d029168dee6d55834ef8cfdc9d01272149ac7b427a507a

Tx prefix hash: 4f4ad71b7488a39e9a2b96c30f1dbfad16c0955347df8624bb0bf61f0487f1c0
Tx public key: 0cfa37d6e4814d522da86f928587b65fd64f6fbdaf10cb2f5f31c8f7e5cd652a
Timestamp: 1778994815 Timestamp [UTC]: 2026-05-17 05:13:35 Age [y:d:h:m:s]: 00:188:02:13:30
Block: 1535634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 147620 RingCT/type: yes/0
Extra: 010cfa37d6e4814d522da86f928587b65fd64f6fbdaf10cb2f5f31c8f7e5cd652a

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f106467919fd799a81436d00d0f9f27b49e4c5d2428f64c21a53f4d420a74d15 0.000600000000 2025580 of 15 <46>

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": 1535644, "vin": [ { "gen": { "height": 1535634 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "f106467919fd799a81436d00d0f9f27b49e4c5d2428f64c21a53f4d420a74d15", "view_tag": "46" } } } ], "extra": [ 1, 12, 250, 55, 214, 228, 129, 77, 82, 45, 168, 111, 146, 133, 135, 182, 95, 214, 79, 111, 189, 175, 16, 203, 47, 95, 49, 200, 247, 229, 205, 101, 42 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: