← previous blocknext block →recent activity
Analyzing
Block #102,178,240
23 transactions · 20 stateful · 2026-09-05 11:55:28 UTC
Parallelism
65/100
Blocked
70%
Avg conflicts / tx
1.7
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,178,240 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w07w110w011w112w213w314w415w516w118w619w720w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x165fe1f0…859f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…641f
0x34b655…2a6f
10 touches
10 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
10 touches
10 conflicts
0x56a284d9…32e4
0x34b655…2a6f
10 touches
10 conflicts
0xa4e9800f…4ab0
0x34b655…2a6f
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 0x165fe1f00b…83859f
Audit this contract →
← previous block·next block →recent activity