← previous blocknext block →recent activity
Analyzing
Block #89,548,741
19 transactions · 18 stateful · 2026-07-23 02:33:46 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,548,741 · 19 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
3w04w15w26w310w112w413w415w216w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x32409e80…a396
0x34b655…2a6f
4 touches
1 conflict
0x44b80fe8…bfa7
0x34b655…2a6f
4 touches
1 conflict
0x519e0fef…7303
0x34b655…2a6f
4 touches
1 conflict
0x9ed87a17…47f4
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity