← previous blocknext block →recent activity
Analyzing
Block #102,641,414
22 transactions · 20 stateful · 2026-09-07 03:02:04 UTC
Parallelism
77/100
Blocked
40%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,641,414 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w08w19w215w216w318w319w420w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbc4bdf7…c62f
0x34b655…2a6f
6 touches
3 conflicts
0xf3aab782…a0dc
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xfa5537c0…b528
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eec
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
3 conflicts on slot 0xbbc4bdf713…b3c62f
Audit this contract →
← previous block·next block →recent activity