← previous blocknext block →recent activity
Analyzing
Block #90,698,077
16 transactions · 14 stateful · 2026-07-27 06:18:02 UTC
Parallelism
69/100
Blocked
43%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,698,077 · 16 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
1w03w05w08w19w110w211w114w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08330b36…ae29
0x34b655…2a6f
4 touches
1 conflict
0x182f914b…44c7
0x34b655…2a6f
4 touches
1 conflict
0x281e160c…fdf2
0x34b655…2a6f
4 touches
1 conflict
0x34731625…2ad4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x53d6f1c9…16c4
0x34b655…2a6f
4 touches
1 conflict
0x5e47cbde…9659
0x34b655…2a6f
4 touches
1 conflict
0x69c491e3…98d9
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
1 conflict on slot 0x08330b3687…a7ae29
Audit this contract →
← previous block·next block →recent activity