← previous blocknext block →recent activity
Analyzing
Block #91,109,193
16 transactions · 14 stateful · 2026-07-28 16:47:17 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,109,193 · 16 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
1w02w16w07w18w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc58c80b…ff79
0x34b655…2a6f
10 touches
10 conflicts
0x124a2fe8…2ea9
0x34b655…2a6f
6 touches
3 conflicts
0x076e4b80…4d01
0x34b655…2a6f
4 touches
1 conflict
0x213a54fa…c85f
0x34b655…2a6f
4 touches
1 conflict
0x31cf4f14…af5e
0x34b655…2a6f
4 touches
1 conflict
0x48579e45…2d8c
0x34b655…2a6f
4 touches
1 conflict
0x4a1a64d1…3771
0x34b655…2a6f
4 touches
1 conflict
0x729817ff…f2fd
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
10 conflicts on slot 0xcc58c80b6c…80ff79
Audit this contract →
← previous block·next block →recent activity