← previous blocknext block →recent activity
Analyzing
Block #102,382,417
30 transactions · 29 stateful · 2026-09-06 05:09:59 UTC
Parallelism
87/100
Blocked
17%
Avg conflicts / tx
0.27
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,382,417 · 30 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
3w04w18w015w116w217w319w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d2d23d3…8a3a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4dffc33e…068d
0x34b655…2a6f
4 touches
1 conflict
0x53f7214d…8ec6
0x34b655…2a6f
4 touches
1 conflict
0x71892c70…660d
0x34b655…2a6f
4 touches
1 conflict
0x77c4faed…1b22
0x34b655…2a6f
4 touches
1 conflict
0x79ec4509…1f61
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
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 0x0d2d23d3eb…148a3a
Audit this contract →
← previous block·next block →recent activity