← previous blocknext block →recent activity
Analyzing
Block #94,792,958
22 transactions · 17 stateful · 2026-08-10 13:57:34 UTC
Parallelism
82/100
Blocked
47%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,792,958 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w08w09w111w112w213w014w215w116w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6000ba5…8d65
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x2491d756…b71c
0xa6afd3…d132
6 touches
3 conflicts
0xff2ebd08…1a7a
0xa6afd3…d132
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x6847107a…f468
0xa6afd3…d132
4 touches
1 conflict
0xc6b9bb4b…145a
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 0xc6000ba5c1…988d65
Audit this contract →
← previous block·next block →recent activity