← previous blocknext block →recent activity
Analyzing
Block #89,751,444
12 transactions · 11 stateful · 2026-07-23 22:34:01 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,751,444 · 12 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
2w04w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x038b9243…553d
0x34b655…2a6f
2 touches
0 conflicts
0x2fdfe038…c16c
0x34b655…2a6f
2 touches
0 conflicts
0x302214a4…3227
0x34b655…2a6f
2 touches
0 conflicts
0x48e3acd8…cf41
0x34b655…2a6f
2 touches
0 conflicts
0x4ab0fef9…caef
0x34b655…2a6f
2 touches
0 conflicts
0x4ccb5334…7c73
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity