← previous blocknext block →recent activity
Analyzing
Block #92,434,078
16 transactions · 16 stateful · 2026-08-02 07:53:59 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,434,078 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w412w013w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1614119…8743
0x7b9256…1fb2
10 touches
10 conflicts
0x177211e2…1c2d
0x754704…b603
10 touches
10 conflicts
0xe1f61186…e2f8
0x754704…b603
10 touches
10 conflicts
0x00000000…0006
0x7b9256…1fb2
10 touches
10 conflicts
0x8aa6d705…bc7e
0x7b9256…1fb2
10 touches
10 conflicts
0x8aa6d705…bc7f
0x7b9256…1fb2
10 touches
10 conflicts
0xb1614119…8746
0x7b9256…1fb2
10 touches
10 conflicts
0xb1614119…8742
0x7b9256…1fb2
10 touches
10 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0x7b9256fd…e21fb2
10 conflicts on slot 0xb1614119bf…438743
Audit this contract →
← previous block·next block →recent activity