← previous blocknext block →recent activity
Analyzing
Block #91,065,004
7 transactions · 7 stateful · 2026-07-28 13:04:54 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,065,004 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2464f36f…724c
0x34b655…2a6f
4 touches
1 conflict
0x6dea4dbf…ba54
0x34b655…2a6f
4 touches
1 conflict
0xe33ef400…df49
0x34b655…2a6f
4 touches
1 conflict
0x051e1801…1126
0x34b655…2a6f
2 touches
0 conflicts
0x0db5eb23…35be
0x34b655…2a6f
2 touches
0 conflicts
0x0f1f4b3a…c378
0x34b655…2a6f
2 touches
0 conflicts
0x15c22181…1354
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
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 0x2464f36f25…ad724c
Audit this contract →
← previous block·next block →recent activity