← previous blocknext block →recent activity
Analyzing
Block #94,490,940
83 transactions · 83 stateful · 2026-08-09 12:37:02 UTC
Parallelism
96/100
Blocked
4%
Avg conflicts / tx
0.05
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,490,940 · 83 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
2w03w14w078w179w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x70eec2ed…f791
0x34b655…2a6f
4 touches
1 conflict
0xfa1e89f0…3f5f
0x065c9d…c394
4 touches
1 conflict
0x312529c0…cd3c
0x34b655…2a6f
4 touches
1 conflict
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0xcfe06a18…b5b5
0x2b46c0…1669
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
3 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity