← previous blocknext block →recent activity
Analyzing
Block #89,828,829
11 transactions · 10 stateful · 2026-07-24 05:04:34 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,828,829 · 11 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19afd281…9cc6
0x34b655…2a6f
4 touches
1 conflict
0x3fa1fac4…826c
0x34b655…2a6f
4 touches
1 conflict
0x02094616…efb5
0x34b655…2a6f
2 touches
0 conflicts
0x0bdb6d2e…9609
0x34b655…2a6f
2 touches
0 conflicts
0x278686dc…698d
0x34b655…2a6f
2 touches
0 conflicts
0x2bc5e7a5…ccb7
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x19afd28192…4b9cc6
Audit this contract →
← previous block·next block →recent activity