← previous blocknext block →recent activity
Analyzing
Block #91,409,542
20 transactions · 19 stateful · 2026-07-29 17:59:35 UTC
Parallelism
70/100
Blocked
42%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,409,542 · 20 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
2w05w06w17w210w311w412w415w416w517w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67e40f97…21a8
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x8eef368f…aa21
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x202ef307…0f25
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x5655f5c3…6b75
0x34b655…2a6f
4 touches
1 conflict
0x629e3ed4…b8b9
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 0x67e40f9738…8421a8
Audit this contract →
← previous block·next block →recent activity