Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1879e354ffcb02132e50636beaa217c55dc09c3394b6dd887cdee3d3d8e44296

Tx prefix hash: ffeed071a3fd3b92af0292917bbdb40d3b089279e8e751875ce06c9d00de48d1
Tx public key: 2578a86a8f060cbb2fe1cbcdbaee3becfaf492f87116a9d2b8d990d12e55582a
Timestamp: 1711771744 Timestamp [UTC]: 2024-03-30 04:09:04 Age [y:d:h:m:s]: 02:043:20:24:13
Block: 989360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 543111 RingCT/type: yes/0
Extra: 012578a86a8f060cbb2fe1cbcdbaee3becfaf492f87116a9d2b8d990d12e55582a02110000000359dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c934738597a216316a49411d159822ba784c5ecec88213cdca5ebbf67b4d98f0 0.000600000000 1449657 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": 989370, "vin": [ { "gen": { "height": 989360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c934738597a216316a49411d159822ba784c5ecec88213cdca5ebbf67b4d98f0" } } ], "extra": [ 1, 37, 120, 168, 106, 143, 6, 12, 187, 47, 225, 203, 205, 186, 238, 59, 236, 250, 244, 146, 248, 113, 22, 169, 210, 184, 217, 144, 209, 46, 85, 88, 42, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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: