← previous blocknext block →recent activity
Analyzing
Block #102,307,563
24 transactions · 22 stateful · 2026-09-05 22:50:41 UTC
Parallelism
75/100
Blocked
32%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,307,563 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
9w011w116w217w318w420w521w022w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb64e0917…33dc
0x34b655…2a6f
10 touches
10 conflicts
0x24ed74ea…a3ff
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x8898c3b2…3aae
0x34b655…2a6f
8 touches
6 conflicts
0x65ff54af…aa01
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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 0xb64e0917f1…d733dc
Audit this contract →
← previous block·next block →recent activity