← previous blocknext block →recent activity
Analyzing
Block #90,703,988
16 transactions · 14 stateful · 2026-07-27 06:47:45 UTC
Parallelism
75/100
Blocked
57%
Avg conflicts / tx
0.81
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,703,988 · 16 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
1w02w13w25w06w18w110w211w213w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91803cbc…2f15
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x08330b36…ae29
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4ca2a6c3…ab80
0x34b655…2a6f
4 touches
1 conflict
0x5f2a5dfd…1ed2
0x34b655…2a6f
4 touches
1 conflict
0x65104f89…bbce
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0x91803cbc00…8c2f15
Audit this contract →
← previous block·next block →recent activity