Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7199558b2baa63f6afbc8de08d34609350cacb9f83f8c9a747bf2964e4ea61df

Tx prefix hash: 717b8929c88cddcc1d9134bbe47f3a53009ead9961372ddcfc0800adc763f477
Tx public key: 667e2783cde7d9076ac59ed42b305ed1f3b712e8896283d27a2616746cdc5cbc
Timestamp: 1774081110 Timestamp [UTC]: 2026-03-21 08:18:30 Age [y:d:h:m:s]: 00:242:01:43:42
Block: 1502499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178554 RingCT/type: yes/0
Extra: 01667e2783cde7d9076ac59ed42b305ed1f3b712e8896283d27a2616746cdc5cbc021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5d2c32ea2864e85b57fe5756ec815db1ecba46a486f201f3973b4fa9e6c289e9 0.000600000000 1992197 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": 1502509, "vin": [ { "gen": { "height": 1502499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d2c32ea2864e85b57fe5756ec815db1ecba46a486f201f3973b4fa9e6c289e9" } } ], "extra": [ 1, 102, 126, 39, 131, 205, 231, 217, 7, 106, 197, 158, 212, 43, 48, 94, 209, 243, 183, 18, 232, 137, 98, 131, 210, 122, 38, 22, 116, 108, 220, 92, 188, 2, 17, 0, 0, 0, 1, 228, 245, 25, 63, 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: