← previous blocknext block →recent activity
Analyzing
Block #89,745,461
16 transactions · 15 stateful · 2026-07-23 22:03:47 UTC
Parallelism
81/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,745,461 · 16 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
6w09w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x2697123c…8526
0x34b655…2a6f
2 touches
0 conflicts
0x49704b15…c584
0x34b655…2a6f
2 touches
0 conflicts
0x6d11d4a8…3a2d
0x34b655…2a6f
2 touches
0 conflicts
0x7cfe59e0…2ec1
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity