Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a58e16a0fa3359ee9465309e0c85ef389ddf5ea115af6ca848b1b42b68d6de98

Tx prefix hash: fcfe7cc7de20b5cede3ab655abcd320349b320c57919ae120520069bc7a0a0b8
Tx public key: a5bcf9e21488b2fdca12aa5154f4b307854b967e24decb5dc21f7192781fa096
Timestamp: 1630003653 Timestamp [UTC]: 2021-08-26 18:47:33 Age [y:d:h:m:s]: 04:244:20:24:17
Block: 321342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1200166 RingCT/type: yes/0
Extra: 01a5bcf9e21488b2fdca12aa5154f4b307854b967e24decb5dc21f7192781fa09602110000006f0441b428000000000000000000

1 output(s) for total of 0.052877215114 xmr

stealth address amount amount idx tag
00: 2ba552d98b323e98c5b174b59f3e91045c0a8faf1d5b0b8cc8c5d884f3387ea7 0.052877215114 667112 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": 321352, "vin": [ { "gen": { "height": 321342 } } ], "vout": [ { "amount": 52877215114, "target": { "key": "2ba552d98b323e98c5b174b59f3e91045c0a8faf1d5b0b8cc8c5d884f3387ea7" } } ], "extra": [ 1, 165, 188, 249, 226, 20, 136, 178, 253, 202, 18, 170, 81, 84, 244, 179, 7, 133, 75, 150, 126, 36, 222, 203, 93, 194, 31, 113, 146, 120, 31, 160, 150, 2, 17, 0, 0, 0, 111, 4, 65, 180, 40, 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: