Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f70bd5f39538d994a23fbe8fa72b59103778fbe0ee1545df909d0efdbf5230c

Tx prefix hash: b78e124f5aa94883451cee8cf2260b19bababc85749997af92fae937ebddf382
Tx public key: c113954e54ee8614aff2cb6f2312175b467def80e52e96d6a9f3976fa57b99e8
Timestamp: 1783199921 Timestamp [UTC]: 2026-07-04 21:18:41 Age [y:d:h:m:s]: 00:137:23:53:03
Block: 1574758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 107403 RingCT/type: yes/0
Extra: 01c113954e54ee8614aff2cb6f2312175b467def80e52e96d6a9f3976fa57b99e8020822c3b5e56ba2c912

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 07cc5ff74f1a7e258c35103d5fb7e1a70ff32e42e073a4bda6a0e0d150f72861 0.000600000000 2064740 of 15 <23>

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": 1574768, "vin": [ { "gen": { "height": 1574758 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "07cc5ff74f1a7e258c35103d5fb7e1a70ff32e42e073a4bda6a0e0d150f72861", "view_tag": "23" } } } ], "extra": [ 1, 193, 19, 149, 78, 84, 238, 134, 20, 175, 242, 203, 111, 35, 18, 23, 91, 70, 125, 239, 128, 229, 46, 150, 214, 169, 243, 151, 111, 165, 123, 153, 232, 2, 8, 34, 195, 181, 229, 107, 162, 201, 18 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: