← previous blocknext block →recent activity
Analyzing
Block #94,229,395
13 transactions · 10 stateful · 2026-08-08 14:29:57 UTC
Parallelism
62/100
Blocked
40%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,229,395 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc16e44c4…ef0c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe8d58d34…426d
0x34b655…2a6f
4 touches
1 conflict
0xeeb194db…499e
0x34b655…2a6f
4 touches
1 conflict
0x42c27cea…b5f3
0x34b655…2a6f
4 touches
1 conflict
0xfa48b154…9988
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 0xc16e44c440…d5ef0c
Audit this contract →
← previous block·next block →recent activity