Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49a659ce47c9ac9c7e007ee8580eabfd8739e57041f7c5198475c6cf926f5acf

Tx prefix hash: 374ec991579cfac85e8b79943b3299d2a759c7eb453473164a460523f8972f6c
Tx public key: a4197df294a1232edb8f2292bec7749ecada68f2f65d28008f7bb37b89c2fecc
Timestamp: 1741938562 Timestamp [UTC]: 2025-03-14 07:49:22 Age [y:d:h:m:s]: 01:253:03:28:01
Block: 1238981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444513 RingCT/type: yes/0
Extra: 01a4197df294a1232edb8f2292bec7749ecada68f2f65d28008f7bb37b89c2fecc021100000004007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3e17f0c2029cab64a0bd3edccc0266fa7a22ebe392d51eff67616f14c347db0b 0.000600000000 1725946 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": 1238991, "vin": [ { "gen": { "height": 1238981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e17f0c2029cab64a0bd3edccc0266fa7a22ebe392d51eff67616f14c347db0b" } } ], "extra": [ 1, 164, 25, 125, 242, 148, 161, 35, 46, 219, 143, 34, 146, 190, 199, 116, 158, 202, 218, 104, 242, 246, 93, 40, 0, 143, 123, 179, 123, 137, 194, 254, 204, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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: