← previous blocknext block →recent activity
Analyzing
Block #93,369,497
44 transactions · 42 stateful · 2026-08-05 14:21:29 UTC
Parallelism
61/100
Blocked
69%
Avg conflicts / tx
2.68
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #93,369,497 · 44 txs across 17 waves · depth 17
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
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w26w07w08w19w210w313w314w415w516w623w1024w1127w128w1229w1330w234w335w436w538w1339w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0x2c390858…b1ed
0x34b655…2a6f
12 touches
15 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
12 touches
15 conflicts
0xac8a5059…fd42
0x34b655…2a6f
12 touches
15 conflicts
0x3464bbc5…a323
0xa6afd3…d132
10 touches
10 conflicts
0x808129fc…f97d
0x34b655…2a6f
10 touches
10 conflicts
0xa279b18d…63bc
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 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
28 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity