← previous blocknext block →recent activity
Analyzing
Block #93,437,520
14 transactions · 14 stateful · 2026-08-05 20:03:29 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,437,520 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w27w49w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x092dba60…2f41
0x968279…9342
6 touches
3 conflicts
0x092dba60…2f43
0x968279…9342
6 touches
3 conflicts
0x1b157552…a138
0x968279…9342
6 touches
3 conflicts
0x1b157552…a13d
0x968279…9342
6 touches
3 conflicts
0x1b157552…a13c
0x968279…9342
6 touches
3 conflicts
0x1b157552…a139
0x968279…9342
6 touches
3 conflicts
0xf4f9cac7…fd98
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity