← previous blocknext block →recent activity
Analyzing
Block #92,349,114
8 transactions · 7 stateful · 2026-08-02 00:46:43 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,349,114 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4fb86cd0…c67b
0x34b655…2a6f
4 touches
1 conflict
0x4fb86cd0…c67c
0x34b655…2a6f
4 touches
1 conflict
0x5649379f…d9eb
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x80e8b019…a3e7
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
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: Perpl
1 conflict on slot 0x4fb86cd027…a5c67b
Audit this contract →
← previous block·next block →recent activity