← previous blocknext block →recent activity
Analyzing
Block #100,142,628
21 transactions · 21 stateful · 2026-08-29 08:58:34 UTC
Parallelism
48/100
Blocked
52%
Avg conflicts / tx
2
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #100,142,628 · 21 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w17w28w39w410w512w614w715w816w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ed1f9d0…fc7f
0x34b655…2a6f
16 touches
28 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
0xc824469a…6426
0x34b655…2a6f
12 touches
15 conflicts
0x2de59be7…3f31
0x34b655…2a6f
8 touches
6 conflicts
0xe21a94dd…4838
0x34b655…2a6f
8 touches
6 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
8 touches
6 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 0x5ed1f9d00b…62fc7f
Audit this contract →
← previous block·next block →recent activity