← previous blocknext block →recent activity
Analyzing
Block #91,248,395
11 transactions · 10 stateful · 2026-07-29 04:27:34 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,248,395 · 11 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
2w04w15w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e6b8ec7…2197
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x6953c299…0910
0x34b655…2a6f
4 touches
1 conflict
0x86d1a3fb…ed61
0x34b655…2a6f
4 touches
1 conflict
0x96ab3f1e…3322
0x34b655…2a6f
4 touches
1 conflict
0xab57dfcf…6713
0x34b655…2a6f
4 touches
1 conflict
0x3eebda21…c64c
0x34b655…2a6f
4 touches
1 conflict
0xad828968…49e4
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
6 conflicts on slot 0x6e6b8ec76e…cb2197
Audit this contract →
← previous block·next block →recent activity