← previous blocknext block →recent activity
Analyzing
Block #93,463,269
17 transactions · 16 stateful · 2026-08-05 22:12:56 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,463,269 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w38w09w110w011w412w513w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fd87a64…6651
0x34b655…2a6f
12 touches
15 conflicts
0x9ba6ae4a…90cb
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xeee8c073…e331
0x34b655…2a6f
6 touches
3 conflicts
0x0728ec77…146c
0x34b655…2a6f
6 touches
3 conflicts
0x206f4379…e08a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
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 0x0fd87a64db…786651
Audit this contract →
← previous block·next block →recent activity