← previous blocknext block →recent activity
Analyzing
Block #93,200,372
15 transactions · 13 stateful · 2026-08-05 00:11:10 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,200,372 · 15 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
2w03w04w16w07w18w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa69ba9e8…e56a
0x34b655…2a6f
6 touches
3 conflicts
0x6c0e32fc…a6ca
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd30f9e74…d404
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0xa69ba9e806…2de56a
Audit this contract →
← previous block·next block →recent activity