← previous blocknext block →recent activity
Analyzing
Block #94,999,865
18 transactions · 17 stateful · 2026-08-11 07:18:17 UTC
Parallelism
50/100
Blocked
59%
Avg conflicts / tx
1.94
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #94,999,865 · 18 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w18w29w414w515w617w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x7a8cad7f…48cd
0x34b655…2a6f
4 touches
1 conflict
0x9d6d235c…3d64
0x34b655…2a6f
4 touches
1 conflict
0x83fd1f41…dfd0
0x065c9d…c394
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
28 conflicts on slot 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity