← previous blocknext block →recent activity
Analyzing
Block #102,255,090
29 transactions · 28 stateful · 2026-09-05 18:24:46 UTC
Parallelism
69/100
Blocked
54%
Avg conflicts / tx
2.21
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #102,255,090 · 29 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w28w39w410w525w626w727w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xd17580f9…ece1
0x754704…b603
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0xa9d11061…b7e9
0x34b655…2a6f
8 touches
6 conflicts
0x042b4bd1…b4d8
0x34b655…2a6f
6 touches
3 conflicts
0x5150abbe…43c3
0x34b655…2a6f
6 touches
3 conflicts
0x9df862dc…7e3b
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
36 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity