← previous blocknext block →recent activity
Analyzing
Block #91,106,132
23 transactions · 20 stateful · 2026-07-28 16:31:53 UTC
Parallelism
83/100
Blocked
50%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,106,132 · 23 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
1w02w13w04w05w16w17w28w09w312w013w114w115w220w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1dfd5cf…0f25
0x34b655…2a6f
6 touches
3 conflicts
0x7be3246e…f89f
0x34b655…2a6f
6 touches
3 conflicts
0x1526b11f…8b21
0x34b655…2a6f
4 touches
1 conflict
0x27754bd4…96ae
0x34b655…2a6f
4 touches
1 conflict
0x329f2f7d…dcff
0x34b655…2a6f
4 touches
1 conflict
0x4fc77cd7…fc9a
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
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 0xb1dfd5cfb5…790f25
Audit this contract →
← previous block·next block →recent activity