← previous blocknext block →recent activity
Analyzing
Block #89,855,191
10 transactions · 9 stateful · 2026-07-24 07:17:28 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,855,191 · 10 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
6w07w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67f87cdf…e5b6
0x34b655…2a6f
4 touches
1 conflict
0xda27c764…7fab
0x34b655…2a6f
4 touches
1 conflict
0x52ee222c…3e0f
0x34b655…2a6f
4 touches
1 conflict
0xaa895bad…ab5f
0x0c65a0…0852
2 touches
0 conflicts
0xe3e67fe3…e754
0x158622…375e
2 touches
0 conflicts
0x2b5101ac…090b
0x34b655…2a6f
2 touches
0 conflicts
0x32e4c206…a476
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
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 0x67f87cdf50…cde5b6
Audit this contract →
← previous block·next block →recent activity