← previous blocknext block →recent activity
Analyzing
Block #91,085,377
13 transactions · 11 stateful · 2026-07-28 14:47:26 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,085,377 · 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
4w05w16w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe53edc5…2d8d
0x34b655…2a6f
4 touches
1 conflict
0xe83f17ba…81fd
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xf4d0bddb…07a4
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x4954a433…820d
0x34b655…2a6f
4 touches
1 conflict
0x4fc141d9…bb36
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 0xfe53edc53e…792d8d
Audit this contract →
← previous block·next block →recent activity