← previous blocknext block →recent activity
Analyzing
Block #93,671,276
20 transactions · 18 stateful · 2026-08-06 15:38:36 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,671,276 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w28w19w210w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8aea13db…5f7f
0x34b655…2a6f
8 touches
6 conflicts
0x5952dc3e…d2b9
0x34b655…2a6f
6 touches
3 conflicts
0xd6af8d98…46f9
0x34b655…2a6f
6 touches
3 conflicts
0xd6af8d98…46fa
0x34b655…2a6f
6 touches
3 conflicts
0xe4af4c87…9964
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x5e7e0120…7bb9
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x8aea13db5b…825f7f
Audit this contract →
← previous block·next block →recent activity