← previous blocknext block →recent activity
Analyzing
Block #91,077,159
18 transactions · 17 stateful · 2026-07-28 14:06:04 UTC
Parallelism
72/100
Blocked
59%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,077,159 · 18 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
1w02w13w04w15w26w38w39w410w113w014w115w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x92115abd…ad76
0x34b655…2a6f
6 touches
3 conflicts
0x3f25409b…f92b
0x34b655…2a6f
6 touches
3 conflicts
0x38a6ef6a…4fee
0x34b655…2a6f
4 touches
1 conflict
0x3a996b35…bc8f
0x34b655…2a6f
4 touches
1 conflict
0x3fca0fa5…0c0a
0x34b655…2a6f
4 touches
1 conflict
0x424934c8…f2f1
0x34b655…2a6f
4 touches
1 conflict
0x53bda555…3810
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity