← previous blocknext block →recent activity
Analyzing
Block #91,248,954
16 transactions · 15 stateful · 2026-07-29 04:30:23 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
0.75
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,248,954 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w27w38w412w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5ed96fe…7424
0x34b655…2a6f
6 touches
3 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xb56f0740…7542
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xf5ed96fe56…777424
Audit this contract →
← previous block·next block →recent activity