← previous blocknext block →recent activity
Analyzing
Block #91,024,555
12 transactions · 12 stateful · 2026-07-28 09:41:24 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.42
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,024,555 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w18w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e8471d5…5256
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xacd1b162…bee6
0x34b655…2a6f
4 touches
1 conflict
0xc4c059d8…185d
0x34b655…2a6f
4 touches
1 conflict
0xfe2577ac…677b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
1 conflict on slot 0x2e8471d583…355256
Audit this contract →
← previous block·next block →recent activity