← previous blocknext block →recent activity
Analyzing
Block #102,308,335
22 transactions · 21 stateful · 2026-09-05 22:54:36 UTC
Parallelism
59/100
Blocked
48%
Avg conflicts / tx
1.68
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #102,308,335 · 22 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
2w04w07w18w29w310w413w514w616w717w818w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22f10271…841d
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0x92ab287b…822e
0x34b655…2a6f
8 touches
6 conflicts
0xafe6567a…4f0a
0x34b655…2a6f
6 touches
4 conflicts
0xdba00dff…ea1f
0x34b655…2a6f
6 touches
3 conflicts
0xd895ee0b…d301
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
28 conflicts on slot 0x22f10271ce…96841d
Audit this contract →
← previous block·next block →recent activity