← previous blocknext block →recent activity
Analyzing
Block #102,475,803
18 transactions · 17 stateful · 2026-09-06 13:02:59 UTC
Parallelism
72/100
Blocked
53%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,475,803 · 18 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
1w02w13w25w08w09w110w212w313w114w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0x0ffac39e…6d34
0x34b655…2a6f
6 touches
3 conflicts
0x02372d42…1871
0x34b655…2a6f
6 touches
3 conflicts
0x0ec07cf7…c0c9
0x34b655…2a6f
6 touches
3 conflicts
0xb58ed141…c32e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd4f6a526…ad10
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity