← previous blocknext block →recent activity
Analyzing
Block #89,861,422
12 transactions · 10 stateful · 2026-07-24 07:48:49 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,861,422 · 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
5w09w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf151f7f…3fe4
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x949ac25e…06dc
0x1c8a33…d316
2 touches
0 conflicts
0xab94749e…6100
0x1c8a33…d316
2 touches
0 conflicts
0x054afe69…16e8
0x34b655…2a6f
2 touches
0 conflicts
0x2b5101ac…090b
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 0xaf151f7f4d…143fe4
Audit this contract →
← previous block·next block →recent activity