Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56006f13fc2ded93473fabbcbde00ff5e62c681ca0596cb38137f5d39c8e6048

Tx prefix hash: 30fc15dc755190156d3534afed1a7492fa40031dea852297e327c652be11a9ab
Tx public key: d454c316eaa3cc7a1cf265b650482696a5ea88098ea1d8a904ad4a049cbc6de8
Timestamp: 1771640502 Timestamp [UTC]: 2026-02-21 02:21:42 Age [y:d:h:m:s]: 00:268:17:24:45
Block: 1482333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197532 RingCT/type: yes/0
Extra: 01d454c316eaa3cc7a1cf265b650482696a5ea88098ea1d8a904ad4a049cbc6de8021100000005e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6c7118963418ecc25ecc4e28bcd36f0e605c2b79a079b5796d069db895271afe 0.000600000000 1971725 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": 1482343, "vin": [ { "gen": { "height": 1482333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c7118963418ecc25ecc4e28bcd36f0e605c2b79a079b5796d069db895271afe" } } ], "extra": [ 1, 212, 84, 195, 22, 234, 163, 204, 122, 28, 242, 101, 182, 80, 72, 38, 150, 165, 234, 136, 9, 142, 161, 216, 169, 4, 173, 74, 4, 156, 188, 109, 232, 2, 17, 0, 0, 0, 5, 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: