Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c30bef1d2d05d7752979b626c4d2eb0fba8f171a1a6758becb391aa62351cea1

Tx prefix hash: dbbdcbd517df2844c5570e13aad4575ec4b0b4ed8c4ac38802bc0474940ebe50
Tx public key: dd59c908be16e9dc91b8eff8a8b2f9c6cbca12074e0d95e5042890bcf55ea5d1
Timestamp: 1769870618 Timestamp [UTC]: 2026-01-31 14:43:38 Age [y:d:h:m:s]: 00:293:19:13:15
Block: 1467683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215651 RingCT/type: yes/0
Extra: 01dd59c908be16e9dc91b8eff8a8b2f9c6cbca12074e0d95e5042890bcf55ea5d1021100000009215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3f459526a16e97f3daaa6338238cb8b9fa29f2f2182875dcdb0ffaffa4b1af76 0.000600000000 1956925 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": 1467693, "vin": [ { "gen": { "height": 1467683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f459526a16e97f3daaa6338238cb8b9fa29f2f2182875dcdb0ffaffa4b1af76" } } ], "extra": [ 1, 221, 89, 201, 8, 190, 22, 233, 220, 145, 184, 239, 248, 168, 178, 249, 198, 203, 202, 18, 7, 78, 13, 149, 229, 4, 40, 144, 188, 245, 94, 165, 209, 2, 17, 0, 0, 0, 9, 33, 91, 191, 137, 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: