← previous blocknext block →recent activity
Analyzing
Block #93,373,213
40 transactions · 36 stateful · 2026-08-05 14:40:10 UTC
Parallelism
65/100
Blocked
61%
Avg conflicts / tx
2.25
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #93,373,213 · 40 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w08w19w012w213w014w115w216w317w418w519w620w721w824w925w1027w1128w329w330w431w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
20 touches
45 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0xfed09e59…a493
0x34b655…2a6f
8 touches
6 conflicts
0x02e23b8b…fd9b
0x34b655…2a6f
8 touches
6 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x861e5aef…d32c
0x34b655…2a6f
8 touches
6 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
45 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity