← previous blocknext block →recent activity
Analyzing
Block #90,877,114
12 transactions · 11 stateful · 2026-07-27 21:18:50 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,877,114 · 12 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
1w04w15w26w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x89dc6177…a1fe
0x34b655…2a6f
6 touches
3 conflicts
0x3b64bdff…4cb1
0x34b655…2a6f
4 touches
1 conflict
0x66473027…6780
0x34b655…2a6f
4 touches
1 conflict
0xe7fbfc54…23cd
0x34b655…2a6f
4 touches
1 conflict
0x120a2553…7f53
0x34b655…2a6f
4 touches
1 conflict
0x155e52ca…fac7
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity