← previous blocknext block →recent activity
Analyzing
Block #93,400,706
15 transactions · 14 stateful · 2026-08-05 16:58:24 UTC
Parallelism
80/100
Blocked
21%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,400,706 · 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
2w03w15w09w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66d5e476…8a1f
0x34b655…2a6f
6 touches
3 conflicts
0x43fd3667…094b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x172b2494…0d57
0x34b655…2a6f
4 touches
1 conflict
0x67a56c8b…f955
0x34b655…2a6f
2 touches
0 conflicts
0x7a66856f…8b9f
0x34b655…2a6f
2 touches
0 conflicts
0x9ba6ae4a…90cb
0x34b655…2a6f
2 touches
0 conflicts
0xd6d4be97…1cac
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
3 conflicts on slot 0x66d5e476c0…268a1f
Audit this contract →
← previous block·next block →recent activity