← previous blocknext block →recent activity
Analyzing
Block #91,836,600
23 transactions · 21 stateful · 2026-07-31 05:48:54 UTC
Parallelism
87/100
Blocked
33%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,836,600 · 23 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
2w05w06w07w08w19w114w115w217w119w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb577a4a7…a670
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0a255626…48e1
0x34b655…2a6f
4 touches
1 conflict
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e65
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5babb0df…9cf9
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 0xb577a4a722…10a670
Audit this contract →
← previous block·next block →recent activity