← previous blocknext block →recent activity
Analyzing
Block #89,541,018
13 transactions · 13 stateful · 2026-07-23 01:42:08 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,541,018 · 13 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
5w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8675136…9a01
0x34b655…2a6f
4 touches
1 conflict
0xf1cc9519…84c1
0x34b655…2a6f
4 touches
1 conflict
0x4f7298fc…24db
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
2 touches
0 conflicts
0x1ea0a6bc…6a74
0x2a68ba…90c5
2 touches
0 conflicts
0x2a9e9bd1…5368
0x2a68ba…90c5
2 touches
0 conflicts
0x7e5ea60a…c4a1
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…0002
0x48cba2…b48b
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 0xd867513669…1d9a01
Audit this contract →
← previous block·next block →recent activity