← previous blocknext block →recent activity
Analyzing
Block #89,839,396
11 transactions · 9 stateful · 2026-07-24 05:57:57 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,839,396 · 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
2w05w18w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5a3b1be…8122
0x34b655…2a6f
4 touches
1 conflict
0x3deaf71f…c229
0x34b655…2a6f
4 touches
1 conflict
0x8a72512c…4624
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xee9f03fd…1e57
0x34b655…2a6f
4 touches
1 conflict
0x506e4e56…ca27
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
2 touches
0 conflicts
0x805d08cf…3cfc
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 0xb5a3b1be7c…288122
Audit this contract →
← previous block·next block →recent activity