← previous blocknext block →recent activity
Analyzing
Block #102,417,009
33 transactions · 27 stateful · 2026-09-06 08:05:11 UTC
Parallelism
88/100
Blocked
22%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,417,009 · 33 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w011w112w013w114w015w116w218w325w030w031w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66b937a7…65fd
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x0d2d23d3…8a3a
0x34b655…2a6f
4 touches
1 conflict
0x2c539d94…b63a
0x34b655…2a6f
4 touches
1 conflict
0x483c2974…bee4
0x34b655…2a6f
4 touches
1 conflict
0x60a536a6…ef7a
0x34b655…2a6f
4 touches
1 conflict
0x7b41d5cd…00e6
0x34b655…2a6f
4 touches
1 conflict
0xa242e227…2e45
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x66b937a732…4265fd
Audit this contract →
← previous block·next block →recent activity