← previous blocknext block →recent activity
Analyzing
Block #90,865,960
10 transactions · 10 stateful · 2026-07-27 20:22:44 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,865,960 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x537bdd2d…a5e1
0x34b655…2a6f
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0x3bdd71a2…b6eb
0x34b655…2a6f
4 touches
1 conflict
0x74f95963…01a2
0x34b655…2a6f
4 touches
1 conflict
0x167de262…f61f
0x34b655…2a6f
2 touches
0 conflicts
0x24eaf46d…8c2e
0x34b655…2a6f
2 touches
0 conflicts
0x2a38297c…67c8
0x34b655…2a6f
2 touches
0 conflicts
0x361f4a1b…1f14
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x537bdd2da6…86a5e1
Audit this contract →
← previous block·next block →recent activity