← previous blocknext block →recent activity
Analyzing
Block #94,301,327
14 transactions · 12 stateful · 2026-08-08 20:34:31 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,301,327 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w27w18w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xc550cc48…815d
0x34b655…2a6f
4 touches
1 conflict
0xc550cc48…815e
0x34b655…2a6f
4 touches
1 conflict
0xd15916f1…f2db
0x34b655…2a6f
4 touches
1 conflict
0xf726e2e2…e561
0x34b655…2a6f
4 touches
1 conflict
0xfb6148df…8609
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
3 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity