← previous blocknext block →recent activity
Analyzing
Block #89,545,006
19 transactions · 17 stateful · 2026-07-23 02:08:48 UTC
Parallelism
84/100
Blocked
18%
Avg conflicts / tx
0.16
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,545,006 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w18w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0eaa0bbe…23b7
0x34b655…2a6f
4 touches
1 conflict
0xb900efa2…8624
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x69d0a300…67ef
0x34b655…2a6f
4 touches
1 conflict
0x42e917f7…ed8c
0x34b655…2a6f
2 touches
0 conflicts
0x6c0e32fc…a6ca
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
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 0x0eaa0bbe8f…8223b7
Audit this contract →
← previous block·next block →recent activity