← previous blocknext block →recent activity
Analyzing
Block #102,252,419
22 transactions · 22 stateful · 2026-09-05 18:11:15 UTC
Parallelism
68/100
Blocked
41%
Avg conflicts / tx
1.09
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,252,419 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w28w09w111w012w113w214w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x5150abbe…43c3
0x34b655…2a6f
10 touches
10 conflicts
0xf7fa82d2…f00a
0x34b655…2a6f
10 touches
10 conflicts
0x18e86f02…fa98
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x5ae0591f…3054
0x34b655…2a6f
6 touches
3 conflicts
0x6d1b72ee…6b78
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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity