← previous blocknext block →recent activity
Analyzing
Block #94,221,213
12 transactions · 10 stateful · 2026-08-08 13:48:28 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,221,213 · 12 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa75e0616…c980
0x065c9d…c394
2 touches
0 conflicts
0x0778475b…bd75
0x2a68ba…90c5
2 touches
0 conflicts
0x015e008d…519c
0x34b655…2a6f
2 touches
0 conflicts
0x16838830…6ab2
0x34b655…2a6f
2 touches
0 conflicts
0x2b2cf495…1c6f
0x34b655…2a6f
2 touches
0 conflicts
0x2b2cf495…1c70
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity