← previous blocknext block →recent activity
Analyzing
Block #94,696,549
21 transactions · 19 stateful · 2026-08-10 05:51:10 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,696,549 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w37w412w313w014w115w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xda986c60…862c
0x968279…9342
6 touches
3 conflicts
0x760625c0…edac
0x968279…9342
6 touches
3 conflicts
0xda986c60…8625
0x968279…9342
6 touches
3 conflicts
0xda986c60…8626
0x968279…9342
6 touches
3 conflicts
0xda986c60…8629
0x968279…9342
6 touches
3 conflicts
0xda986c60…862a
0x968279…9342
6 touches
3 conflicts
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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity