Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e2b6b6d25709f9f4511e39dabbabef2d7c648b2781df3aed3a65d871f425c46

Tx prefix hash: 57d62635933639fab71bc7d77482a18a04fdde5cbd591fd1fb76e94d273555d2
Tx public key: 320725815285745d4d32a654dce6fad43bfec6fa0b5a20dfcd96220d374f7bff
Timestamp: 1577923771 Timestamp [UTC]: 2020-01-02 00:09:31 Age [y:d:h:m:s]: 06:130:01:49:35
Block: 36738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1494026 RingCT/type: yes/0
Extra: 01320725815285745d4d32a654dce6fad43bfec6fa0b5a20dfcd96220d374f7bff0211000000124ac5aa02000000000000000000

1 output(s) for total of 0.463816807859 xmr

stealth address amount amount idx tag
00: ba7a2c682fbd31cc2f1be4b627c5a5e793e2850d21a16bf1a852deb2f395df2f 0.463816807859 62280 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": 36748, "vin": [ { "gen": { "height": 36738 } } ], "vout": [ { "amount": 463816807859, "target": { "key": "ba7a2c682fbd31cc2f1be4b627c5a5e793e2850d21a16bf1a852deb2f395df2f" } } ], "extra": [ 1, 50, 7, 37, 129, 82, 133, 116, 93, 77, 50, 166, 84, 220, 230, 250, 212, 59, 254, 198, 250, 11, 90, 32, 223, 205, 150, 34, 13, 55, 79, 123, 255, 2, 17, 0, 0, 0, 18, 74, 197, 170, 2, 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: