← previous blocknext block →recent activity
Analyzing
Block #91,109,596
13 transactions · 13 stateful · 2026-07-28 16:49:19 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,109,596 · 13 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
4w05w16w28w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7d3cccb…fd18
0x34b655…2a6f
4 touches
1 conflict
0x5efd7300…d8a5
0x34b655…2a6f
4 touches
1 conflict
0x7e06d07b…36af
0x34b655…2a6f
4 touches
1 conflict
0x7e06d07b…36b0
0x34b655…2a6f
4 touches
1 conflict
0x821408cd…3dc7
0x34b655…2a6f
4 touches
1 conflict
0xa46bd549…dc12
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0xd7d3cccb6e…16fd18
Audit this contract →
← previous block·next block →recent activity