← previous blocknext block →recent activity
Analyzing
Block #102,404,213
63 transactions · 59 stateful · 2026-09-06 07:00:20 UTC
Parallelism
87/100
Blocked
17%
Avg conflicts / tx
0.54
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,404,213 · 63 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
4w07w08w19w210w111w212w313w415w559w660w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65ff54af…aa01
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0x009b3c65…4334
0x34b655…2a6f
8 touches
6 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
6 touches
3 conflicts
0xc5d0cbe9…5172
0x34b655…2a6f
6 touches
3 conflicts
0xa57d17f0…672a
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
28 conflicts on slot 0x65ff54af45…13aa01
Audit this contract →
← previous block·next block →recent activity