← previous blocknext block →recent activity
Analyzing
Block #91,061,395
23 transactions · 21 stateful · 2026-07-28 12:46:44 UTC
Parallelism
87/100
Blocked
29%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,061,395 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w28w09w117w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x2fa2d1bd…0221
0x34b655…2a6f
4 touches
1 conflict
0x4c619b7d…f4fa
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity