← previous blocknext block →recent activity
Analyzing
Block #89,570,156
13 transactions · 12 stateful · 2026-07-23 04:56:51 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,570,156 · 13 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
2w03w16w17w09w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1fbd24c7…325b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x07217796…0f5c
0x34b655…2a6f
4 touches
1 conflict
0xaffd1480…76b8
0x34b655…2a6f
4 touches
1 conflict
0x459cbb60…8957
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7f4a8466…f2cc
0x2b46c0…1669
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
3 conflicts on slot 0x1fbd24c7f5…59325b
Audit this contract →
← previous block·next block →recent activity