← previous blocknext block →recent activity
Analyzing
Block #89,849,049
16 transactions · 16 stateful · 2026-07-24 06:46:35 UTC
Parallelism
56/100
Blocked
56%
Avg conflicts / tx
1.25
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,849,049 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w28w39w110w411w513w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0bcbbcad…fc9c
0x34b655…2a6f
8 touches
6 conflicts
0x4360b49f…140d
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xafb8e71e…9285
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x44a2c3ff…0abc
0x34b655…2a6f
4 touches
1 conflict
0x4e37574f…4145
0x34b655…2a6f
4 touches
1 conflict
0x65398157…785c
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 0x0bcbbcadb2…bcfc9c
Audit this contract →
← previous block·next block →recent activity