← previous blocknext block →recent activity
Analyzing
Block #91,108,770
14 transactions · 14 stateful · 2026-07-28 16:45:09 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,108,770 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w16w17w29w110w312w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7dfe7788…8d9f
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x3d22c439…de6d
0x34b655…2a6f
4 touches
1 conflict
0x3f010cbf…c7a2
0x34b655…2a6f
4 touches
1 conflict
0x5efd7300…d8a5
0x34b655…2a6f
4 touches
1 conflict
0x60a899fe…e7a2
0x34b655…2a6f
4 touches
1 conflict
0x658c5caa…7fa2
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x7dfe77881e…028d9f
Audit this contract →
← previous block·next block →recent activity