← previous blocknext block →recent activity
Analyzing
Block #102,484,111
21 transactions · 17 stateful · 2026-09-06 13:45:08 UTC
Parallelism
81/100
Blocked
47%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,484,111 · 21 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
1w02w13w24w05w17w012w113w216w217w319w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22f10271…841d
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xdf146090…28f8
0x34b655…2a6f
6 touches
3 conflicts
0x0ebb2cbd…f49e
0x34b655…2a6f
4 touches
1 conflict
0x0ec07cf7…c0c9
0x34b655…2a6f
4 touches
1 conflict
0x02372d42…1871
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 0x22f10271ce…96841d
Audit this contract →
← previous block·next block →recent activity