← previous blocknext block →recent activity
Analyzing
Block #91,904,518
12 transactions · 10 stateful · 2026-07-31 11:30:40 UTC
Parallelism
83/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,904,518 · 12 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
2w04w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2dff59d9…f5e6
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x4984f7be…d515
0x34b655…2a6f
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0x36187d32…57e2
0x34b655…2a6f
2 touches
0 conflicts
0x46c8e565…d7a8
0x34b655…2a6f
2 touches
0 conflicts
0x60f63d67…5ba0
0x34b655…2a6f
2 touches
0 conflicts
0x7840c762…8060
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 0x2dff59d975…70f5e6
Audit this contract →
← previous block·next block →recent activity