← previous blocknext block →recent activity
Analyzing
Block #93,665,510
10 transactions · 8 stateful · 2026-08-06 15:09:36 UTC
Parallelism
70/100
Blocked
25%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,665,510 · 10 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
2w03w14w06w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc351d6d…256b
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x16eaa805…b0b0
0x34b655…2a6f
2 touches
0 conflicts
0x1e56f6b6…5940
0x34b655…2a6f
2 touches
0 conflicts
0x25d292ed…5531
0x34b655…2a6f
2 touches
0 conflicts
0x4984f7be…d515
0x34b655…2a6f
2 touches
0 conflicts
0x69a45f39…39aa
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 0xcc351d6dd2…b1256b
Audit this contract →
← previous block·next block →recent activity