Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 561b574d8cbdb1059068b9b1736b05a306663247d22bb5370d14bcf059a733aa

Tx prefix hash: 5c96f1fb35a4e6299c2b1b555afe4d9fa38215adfbf7acd86b009c51b9994800
Tx public key: e582c71e2bacec9fc7560448ee0cda20bd669b9c2f223fe2d174b70184de508c
Timestamp: 1675668010 Timestamp [UTC]: 2023-02-06 07:20:10 Age [y:d:h:m:s]: 03:203:14:36:11
Block: 690909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 931524 RingCT/type: yes/0
Extra: 01e582c71e2bacec9fc7560448ee0cda20bd669b9c2f223fe2d174b70184de508c021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.003153055387 xmr

stealth address amount amount idx tag
00: f38b5c71cf945a8f7fd2f28b5f3526f18b0420fe7eb8bce370eab9cc4580ddad 0.003153055387 1133647 of 0 -

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": 690919, "vin": [ { "gen": { "height": 690909 } } ], "vout": [ { "amount": 3153055387, "target": { "key": "f38b5c71cf945a8f7fd2f28b5f3526f18b0420fe7eb8bce370eab9cc4580ddad" } } ], "extra": [ 1, 229, 130, 199, 30, 43, 172, 236, 159, 199, 86, 4, 72, 238, 12, 218, 32, 189, 102, 155, 156, 47, 34, 63, 226, 209, 116, 183, 1, 132, 222, 80, 140, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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: