Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b4caeb586e82da21ebe403919ea3fa74f1560718c61ec95081e77e2c8a88c75

Tx prefix hash: 377de38c6373cceaefc9eea2c5e9576ee8fea467fb5e7d50150286340b16656b
Tx public key: 51269d9b5ec9c8283e84a498313ce3446a4662f7403010c18b15ac0150217f4e
Timestamp: 1753787870 Timestamp [UTC]: 2025-07-29 11:17:50 Age [y:d:h:m:s]: 01:112:09:49:09
Block: 1335895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345490 RingCT/type: yes/0
Extra: 0151269d9b5ec9c8283e84a498313ce3446a4662f7403010c18b15ac0150217f4e021100000002ef221485000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 740c7d2b3093b9dc971943990efcdb61a8c5f896c29bc60dca224305b7a9a810 0.000600000000 1823696 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": 1335905, "vin": [ { "gen": { "height": 1335895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "740c7d2b3093b9dc971943990efcdb61a8c5f896c29bc60dca224305b7a9a810" } } ], "extra": [ 1, 81, 38, 157, 155, 94, 201, 200, 40, 62, 132, 164, 152, 49, 60, 227, 68, 106, 70, 98, 247, 64, 48, 16, 193, 139, 21, 172, 1, 80, 33, 127, 78, 2, 17, 0, 0, 0, 2, 239, 34, 20, 133, 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: