Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f2b3a5159be3e029b898aed25f70a92796f4fab5545a6d454bc0f185f4e6a7f

Tx prefix hash: 9ecdadc296d652652665bb890f9c35d12c2c5afe3ff2da8c131fe7ce6d7e6d58
Tx public key: fd22eda3f3403e1d598f79c3f400ada9c064309ad451be91d09fca364b8890cc
Timestamp: 1740055818 Timestamp [UTC]: 2025-02-20 12:50:18 Age [y:d:h:m:s]: 01:274:10:39:04
Block: 1223361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460133 RingCT/type: yes/0
Extra: 01fd22eda3f3403e1d598f79c3f400ada9c064309ad451be91d09fca364b8890cc021100000009007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dd1395b220a36f06aacb706ad78541f10d871322aa5eb705383d233a411ea8b2 0.000600000000 1710218 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": 1223371, "vin": [ { "gen": { "height": 1223361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd1395b220a36f06aacb706ad78541f10d871322aa5eb705383d233a411ea8b2" } } ], "extra": [ 1, 253, 34, 237, 163, 243, 64, 62, 29, 89, 143, 121, 195, 244, 0, 173, 169, 192, 100, 48, 154, 212, 81, 190, 145, 208, 159, 202, 54, 75, 136, 144, 204, 2, 17, 0, 0, 0, 9, 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: