← previous blocknext block →recent activity
Analyzing
Block #91,063,237
14 transactions · 13 stateful · 2026-07-28 12:56:00 UTC
Parallelism
57/100
Blocked
46%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,063,237 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w29w310w411w513w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d94d7d6…6ed4
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xb4e0a934…5fc7
0x34b655…2a6f
6 touches
3 conflicts
0x5cfa06bc…87fb
0x34b655…2a6f
4 touches
1 conflict
0x9c3004b2…5421
0x34b655…2a6f
4 touches
1 conflict
0xa86bb87d…0a7a
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 0x6d94d7d6d7…ed6ed4
Audit this contract →
← previous block·next block →recent activity