← previous blocknext block →recent activity
Analyzing
Block #102,063,221
18 transactions · 17 stateful · 2026-09-05 02:12:11 UTC
Parallelism
61/100
Blocked
47%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,063,221 · 18 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
2w03w04w15w06w17w28w311w412w514w616w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9153e8ee…7171
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x948836ff…59ab
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00f6a8a7…0e6e
0x34b655…2a6f
6 touches
3 conflicts
0x62bb20db…431e
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
21 conflicts on slot 0x9153e8eeea…467171
Audit this contract →
← previous block·next block →recent activity