← previous blocknext block →recent activity
Analyzing
Block #102,311,874
22 transactions · 21 stateful · 2026-09-05 23:12:33 UTC
Parallelism
68/100
Blocked
43%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,311,874 · 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
1w02w13w26w07w111w012w113w215w316w417w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xefb191c9…6f6a
0x34b655…2a6f
10 touches
10 conflicts
0x8898c3b2…3aae
0x34b655…2a6f
9 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xe108b282…58b3
0x34b655…2a6f
8 touches
6 conflicts
0x24ed74ea…a3ff
0x34b655…2a6f
8 touches
6 conflicts
0x0eac7709…66c3
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
15 conflicts on slot 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity