← previous blocknext block →recent activity
Analyzing
Block #89,404,115
13 transactions · 12 stateful · 2026-07-22 10:27:32 UTC
Parallelism
77/100
Blocked
25%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,404,115 · 13 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
2w03w17w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb26fce3e…f47f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x392abd10…f6b1
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0004
0x2b46c0…1669
2 touches
0 conflicts
0x22c902b8…0e30
0x2b46c0…1669
2 touches
0 conflicts
0x0c159059…39b7
0x34b655…2a6f
2 touches
0 conflicts
0x0c53719e…0366
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 0xb26fce3e2d…63f47f
Audit this contract →
← previous block·next block →recent activity