← previous blocknext block →recent activity
Analyzing
Block #89,559,896
8 transactions · 7 stateful · 2026-07-23 03:48:14 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
0.63
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,559,896 · 8 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
2w03w14w25w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4886b3df…67a3
0x34b655…2a6f
6 touches
3 conflicts
0x6d187b4f…9f38
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4984f7be…d515
0x34b655…2a6f
4 touches
1 conflict
0x5e3014f0…b4e1
0x34b655…2a6f
4 touches
1 conflict
0x42d5e8f3…5930
0x34b655…2a6f
2 touches
0 conflicts
0x42d5e8f3…5931
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
3 conflicts on slot 0x4886b3dfcf…0067a3
Audit this contract →
← previous block·next block →recent activity