← previous blocknext block →recent activity
Analyzing
Block #91,130,363
12 transactions · 12 stateful · 2026-07-28 18:33:46 UTC
Parallelism
58/100
Blocked
42%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,130,363 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w06w18w19w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xa47e7349…3072
0x34b655…2a6f
6 touches
3 conflicts
0x54d68470…4b32
0x34b655…2a6f
6 touches
3 conflicts
0x7c0bdc54…9dde
0x34b655…2a6f
6 touches
3 conflicts
0x86977b3d…a9c4
0x34b655…2a6f
6 touches
3 conflicts
0x418f6232…2de6
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x63aeb91f…a6d0
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity