← previous blocknext block →recent activity
Analyzing
Block #93,351,852
26 transactions · 25 stateful · 2026-08-05 12:52:45 UTC
Parallelism
65/100
Blocked
44%
Avg conflicts / tx
1.62
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #93,351,852 · 26 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w510w614w418w719w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0x68c740e2…58d6
0x34b655…2a6f
7 touches
6 conflicts
0xfed09e59…a493
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
21 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity