Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c17858876e3504d0ffd41efc3157bc533ee6c78b443bace35a011681e8d7611d

Tx prefix hash: 2f79d5f24cd72f078e5ea2003526efd55a3fafae9302a04e78e93c9e56b5d42c
Tx public key: 5350a2f5af5f98ecfb976b9546ef19a73c74b108c8c87dd73c5c46e6a8c5cbe8
Timestamp: 1772561224 Timestamp [UTC]: 2026-03-03 18:07:04 Age [y:d:h:m:s]: 00:262:16:39:27
Block: 1489945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193416 RingCT/type: yes/0
Extra: 015350a2f5af5f98ecfb976b9546ef19a73c74b108c8c87dd73c5c46e6a8c5cbe8021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ebd53da7b4757bc671fe17ee454b52d20c7fe1d0395ab33a9fbafdbf81c535c6 0.000600000000 1979443 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": 1489955, "vin": [ { "gen": { "height": 1489945 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ebd53da7b4757bc671fe17ee454b52d20c7fe1d0395ab33a9fbafdbf81c535c6" } } ], "extra": [ 1, 83, 80, 162, 245, 175, 95, 152, 236, 251, 151, 107, 149, 70, 239, 25, 167, 60, 116, 177, 8, 200, 200, 125, 215, 60, 92, 70, 230, 168, 197, 203, 232, 2, 17, 0, 0, 0, 4, 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: