← previous blocknext block →recent activity
Analyzing
Block #89,770,394
15 transactions · 14 stateful · 2026-07-24 00:09:40 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,770,394 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w211w012w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3439dfbc…0d03
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x8a705be8…7ac4
0xc8689a…ee79
4 touches
1 conflict
0x264ae9a2…a29d
0x34b655…2a6f
4 touches
1 conflict
0xe8352ac7…d7a3
0x34b655…2a6f
4 touches
1 conflict
0xeb3f570c…2a91
0x34b655…2a6f
4 touches
1 conflict
0xf5379ea4…bc3f
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
6 conflicts on slot 0x3439dfbcc6…080d03
Audit this contract →
← previous block·next block →recent activity