← previous blocknext block →recent activity
Analyzing
Block #94,170,199
20 transactions · 20 stateful · 2026-08-08 09:29:57 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,170,199 · 20 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
1w02w14w05w16w28w09w112w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0b32e9b…6b1c
0x34b655…2a6f
8 touches
6 conflicts
0xd08098a8…f0a6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x6f2ce3a9…9be3
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xe131df52…7554
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 0xc0b32e9bdb…9f6b1c
Audit this contract →
← previous block·next block →recent activity