← previous blocknext block →recent activity
Analyzing
Block #89,702,538
29 transactions · 26 stateful · 2026-07-23 18:27:02 UTC
Parallelism
93/100
Blocked
12%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,702,538 · 29 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
1w02w123w124w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f7d8a09…362c
0x34b655…2a6f
4 touches
1 conflict
0x58a68b92…6a6e
0x34b655…2a6f
4 touches
1 conflict
0x61e01cd0…b73e
0x34b655…2a6f
4 touches
1 conflict
0x61e01cd0…b73f
0x34b655…2a6f
4 touches
1 conflict
0x751f0341…fe9b
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xe9ef16e7…2d22
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
1 conflict on slot 0x3f7d8a0905…cf362c
Audit this contract →
← previous block·next block →recent activity