← previous blocknext block →recent activity
Analyzing
Block #89,846,434
25 transactions · 20 stateful · 2026-07-24 06:33:25 UTC
Parallelism
84/100
Blocked
45%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,846,434 · 25 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
2w03w14w211w013w114w216w117w218w219w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x0aa283ae…ef9c
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x4fb86cd0…c67b
0x34b655…2a6f
4 touches
1 conflict
0x4fb86cd0…c67c
0x34b655…2a6f
4 touches
1 conflict
0x5649379f…d9eb
0x34b655…2a6f
4 touches
1 conflict
0x56b580bf…f969
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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity