← previous blocknext block →recent activity
Analyzing
Block #89,676,369
19 transactions · 18 stateful · 2026-07-23 16:15:00 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,676,369 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w311w312w413w014w118w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02d895f0…2b93
0x34b655…2a6f
4 touches
1 conflict
0x1dd015c2…edf4
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2bac71c3…3296
0x34b655…2a6f
4 touches
1 conflict
0x2d394d9a…5e85
0x34b655…2a6f
4 touches
1 conflict
0x5dd18eb2…4d66
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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 0x02d895f0dc…af2b93
Audit this contract →
← previous block·next block →recent activity