← previous blocknext block →recent activity
Analyzing
Block #94,836,221
11 transactions · 10 stateful · 2026-08-10 17:35:13 UTC
Parallelism
82/100
Blocked
40%
Avg conflicts / tx
0.36
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,836,221 · 11 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
1w02w13w04w15w06w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe85638e6…207a
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0603347b…5872
0x34b655…2a6f
2 touches
0 conflicts
0x16ef6aaa…6eb2
0x34b655…2a6f
2 touches
0 conflicts
0x2b5101ac…090b
0x34b655…2a6f
2 touches
0 conflicts
0x5f57e7ab…9f8d
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 0xe85638e649…f9207a
Audit this contract →
← previous block·next block →recent activity