Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4de6fa31d64f3e9f3ca5115716f1250bf79b933a92ae9fa2f1526f1e2f89f434

Tx prefix hash: fc243998c4cf8479f7a12583ffc8f5b0fd18a0a3d1cb0a088e2c26c788f96d66
Tx public key: e642371d5b1d88dea16bd2085865a91c436c193f1b9e60d26ad2df7fc3473216
Timestamp: 1784098411 Timestamp [UTC]: 2026-07-15 06:53:31 Age [y:d:h:m:s]: 00:128:11:09:48
Block: 1582716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 100141 RingCT/type: yes/0
Extra: 01e642371d5b1d88dea16bd2085865a91c436c193f1b9e60d26ad2df7fc34732160208fb0f6bac0ca98c93

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 560c807ed0c45b5d68f45535536530220ed885b6bc20ee9ff471e4458a035c0f 0.000600000000 2072710 of 15 <c1>

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": 1582726, "vin": [ { "gen": { "height": 1582716 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "560c807ed0c45b5d68f45535536530220ed885b6bc20ee9ff471e4458a035c0f", "view_tag": "c1" } } } ], "extra": [ 1, 230, 66, 55, 29, 91, 29, 136, 222, 161, 107, 210, 8, 88, 101, 169, 28, 67, 108, 25, 63, 27, 158, 96, 210, 106, 210, 223, 127, 195, 71, 50, 22, 2, 8, 251, 15, 107, 172, 12, 169, 140, 147 ], "rct_signatures": { "type": 0 } }


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