← previous blocknext block →recent activity
Analyzing
Block #102,269,955
52 transactions · 51 stateful · 2026-09-05 19:40:09 UTC
Parallelism
90/100
Blocked
16%
Avg conflicts / tx
0.31
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,269,955 · 52 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w18w29w010w112w213w347w148w449w051w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdf025f81…a7c4
0x34b655…2a6f
10 touches
10 conflicts
0xdcccd149…4cab
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x65ff54af…aa01
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x3cb7ee74…b8a5
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 0xdf025f810d…4fa7c4
Audit this contract →
← previous block·next block →recent activity