← previous blocknext block →recent activity
Analyzing
Block #91,070,999
25 transactions · 24 stateful · 2026-07-28 13:35:03 UTC
Parallelism
84/100
Blocked
29%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,070,999 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w17w08w09w010w113w215w317w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f900be0…cd6e
0x34b655…2a6f
8 touches
6 conflicts
0x92115abd…ad76
0x34b655…2a6f
8 touches
6 conflicts
0x427d1120…4eb1
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
4 touches
1 conflict
0x745a7fd6…5fea
0x34b655…2a6f
4 touches
1 conflict
0x7c93b38a…9e69
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0x6f900be04d…4ccd6e
Audit this contract →
← previous block·next block →recent activity