← previous blocknext block →recent activity
Analyzing
Block #94,856,095
8 transactions · 7 stateful · 2026-08-10 19:15:12 UTC
Parallelism
75/100
Blocked
43%
Avg conflicts / tx
0.38
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,856,095 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a0cecef…4ed0
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x46279ae7…20dd
0x2b46c0…1669
2 touches
0 conflicts
0x7f4a8466…f2cc
0x2b46c0…1669
2 touches
0 conflicts
0x06b4e86e…b0a0
0x34b655…2a6f
2 touches
0 conflicts
0x0c57679c…99c9
0x34b655…2a6f
2 touches
0 conflicts
0x0e22f39d…b92b
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x0a0cecef55…324ed0
Audit this contract →
← previous block·next block →recent activity