← previous blocknext block →recent activity
Analyzing
Block #93,922,835
18 transactions · 16 stateful · 2026-08-07 12:43:43 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,922,835 · 18 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
2w04w05w17w18w19w210w312w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4bcd2b7c…a670
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x809f2ba8…89d3
0x34b655…2a6f
8 touches
6 conflicts
0x48e3acd8…cf41
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x38c6ff01…689f
0x34b655…2a6f
6 touches
3 conflicts
0x574628e9…dcc3
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 0x4bcd2b7cc7…15a670
Audit this contract →
← previous block·next block →recent activity