← previous blocknext block →recent activity
Analyzing
Block #94,807,311
21 transactions · 20 stateful · 2026-08-10 15:09:46 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,807,311 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w38w49w510w611w515w618w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0d45ffd…89cf
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x7726bf58…6524
0x34b655…2a6f
6 touches
3 conflicts
0xfb3eaa03…a56a
0x34b655…2a6f
4 touches
1 conflict
0x7feec70a…fd8a
0x34b655…2a6f
4 touches
1 conflict
0xa2e4453b…a207
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
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
15 conflicts on slot 0xf0d45ffdb0…4089cf
Audit this contract →
← previous block·next block →recent activity