← previous blocknext block →recent activity
Analyzing
Block #92,317,949
17 transactions · 14 stateful · 2026-08-01 22:10:00 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,317,949 · 17 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
2w05w18w012w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb84f537…c9b2
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x41e2ea73…ddf8
0x34b655…2a6f
2 touches
0 conflicts
0x51256436…bc7f
0x34b655…2a6f
2 touches
0 conflicts
0x6b76010d…b508
0x34b655…2a6f
2 touches
0 conflicts
0x923c57f1…7810
0x34b655…2a6f
2 touches
0 conflicts
0x9c5ce778…4b6a
0x34b655…2a6f
2 touches
0 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: Perpl
1 conflict on slot 0xbb84f537ea…aec9b2
Audit this contract →
← previous block·next block →recent activity