← previous blocknext block →recent activity
Analyzing
Block #89,772,478
18 transactions · 15 stateful · 2026-07-24 00:20:11 UTC
Parallelism
83/100
Blocked
53%
Avg conflicts / tx
0.67
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,772,478 · 18 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
2w03w15w16w17w28w09w110w214w015w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x5c79a7db…b7aa
0x34b655…2a6f
4 touches
1 conflict
0x8e8d48a4…7a75
0x34b655…2a6f
4 touches
1 conflict
0x905a2dd7…1dfc
0x34b655…2a6f
4 touches
1 conflict
0x9117fbd3…64bb
0x34b655…2a6f
4 touches
1 conflict
0xc9377f93…3739
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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity