← previous blocknext block →recent activity
Analyzing
Block #91,001,100
15 transactions · 14 stateful · 2026-07-28 07:43:02 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,001,100 · 15 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
4w05w18w09w210w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xacf2813c…1964
0x34b655…2a6f
8 touches
6 conflicts
0xdd190722…ecae
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd957c18f…5cfc
0x34b655…2a6f
6 touches
3 conflicts
0x55723bd8…6955
0x34b655…2a6f
4 touches
1 conflict
0x6841aa96…97ae
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
6 conflicts on slot 0xacf2813cab…e91964
Audit this contract →
← previous block·next block →recent activity