Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be2a8429f36f1f1200396fc90f421101fe2aa35872fae7bc9bb0c07de24a85c4

Tx prefix hash: d20901d88396617f94eeb5ece49975f48c1cfe6bfd5c3b79b3ee3d213958e5c5
Tx public key: 73a2a34c66bb4466ad131942d0ce6bd79b9a6a7a89cca1fa3f526cfac7420129
Timestamp: 1762030927 Timestamp [UTC]: 2025-11-01 21:02:07 Age [y:d:h:m:s]: 01:016:12:15:57
Block: 1402896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278137 RingCT/type: yes/0
Extra: 0173a2a34c66bb4466ad131942d0ce6bd79b9a6a7a89cca1fa3f526cfac7420129021100000002e4dc9009000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bd4635f96917c3d5b317dfa37ff4d2c0d8b800a3ed3b4c97cf729e77636a04c0 0.000600000000 1891221 of 15 -

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": 1402906, "vin": [ { "gen": { "height": 1402896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd4635f96917c3d5b317dfa37ff4d2c0d8b800a3ed3b4c97cf729e77636a04c0" } } ], "extra": [ 1, 115, 162, 163, 76, 102, 187, 68, 102, 173, 19, 25, 66, 208, 206, 107, 215, 155, 154, 106, 122, 137, 204, 161, 250, 63, 82, 108, 250, 199, 66, 1, 41, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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: