← previous blocknext block →recent activity
Analyzing
Block #93,361,541
29 transactions · 24 stateful · 2026-08-05 13:41:29 UTC
Parallelism
66/100
Blocked
58%
Avg conflicts / tx
1.34
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #93,361,541 · 29 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w06w110w211w312w413w516w317w618w719w825w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe316a1f9…1966
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xa558e115…fc88
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x0110331c…b891
0x34b655…2a6f
6 touches
3 conflicts
0x20492d53…80f9
0x34b655…2a6f
6 touches
3 conflicts
0x4984f7be…d515
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
15 conflicts on slot 0xe316a1f9dc…b61966
Audit this contract →
← previous block·next block →recent activity