← previous blocknext block →recent activity
Analyzing
Block #102,218,722
27 transactions · 27 stateful · 2026-09-05 15:20:30 UTC
Parallelism
63/100
Blocked
56%
Avg conflicts / tx
1.56
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #102,218,722 · 27 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w18w19w210w313w014w115w216w317w419w420w521w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xdc9deb0a…4285
0x34b655…2a6f
10 touches
10 conflicts
0x256918f1…c4d0
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0xa4e9800f…4ab0
0x34b655…2a6f
8 touches
6 conflicts
0x1f396cee…862f
0x34b655…2a6f
8 touches
6 conflicts
0x2c539d94…b63a
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity