← previous blocknext block →recent activity
Analyzing
Block #102,279,790
21 transactions · 20 stateful · 2026-09-05 20:30:03 UTC
Parallelism
57/100
Blocked
50%
Avg conflicts / tx
1.62
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #102,279,790 · 21 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
4w07w18w29w312w413w514w618w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x256918f1…c4d0
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xd66696e0…0842
0x34b655…2a6f
12 touches
15 conflicts
0x948836ff…59ab
0x34b655…2a6f
8 touches
6 conflicts
0x75650dc7…d8d7
0x34b655…2a6f
8 touches
6 conflicts
0x160cd79a…3468
0x34b655…2a6f
6 touches
3 conflicts
0x588380ee…0a5c
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 0x256918f186…59c4d0
Audit this contract →
← previous block·next block →recent activity