Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d038aed04aa799c664b16549f70a2d112b52eeff5d1c7ff0081efb619f04049c

Tx prefix hash: cf89cda3557bf93f479bc4e7c4733f8eaa6f91e9d957e7ab1d1ae5bf75528528
Tx public key: 6ec5853f0e7584c6a22748074e3f7ec23af6cfb940a85532aafa121a967e0653
Timestamp: 1575942700 Timestamp [UTC]: 2019-12-10 01:51:40 Age [y:d:h:m:s]: 06:345:09:51:17
Block: 24373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1656735 RingCT/type: yes/0
Extra: 016ec5853f0e7584c6a22748074e3f7ec23af6cfb940a85532aafa121a967e06530211000000089159db1e000000000000000000

1 output(s) for total of 0.509615940252 xmr

stealth address amount amount idx tag
00: 308a3522645f34f72fd570b9d8d6a446bb3c48dcece1592f7e85aded9de9bd1b 0.509615940252 40044 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": 24383, "vin": [ { "gen": { "height": 24373 } } ], "vout": [ { "amount": 509615940252, "target": { "key": "308a3522645f34f72fd570b9d8d6a446bb3c48dcece1592f7e85aded9de9bd1b" } } ], "extra": [ 1, 110, 197, 133, 63, 14, 117, 132, 198, 162, 39, 72, 7, 78, 63, 126, 194, 58, 246, 207, 185, 64, 168, 85, 50, 170, 250, 18, 26, 150, 126, 6, 83, 2, 17, 0, 0, 0, 8, 145, 89, 219, 30, 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: