← previous blocknext block →recent activity
Analyzing
Block #100,140,630
23 transactions · 19 stateful · 2026-08-29 08:48:30 UTC
Parallelism
65/100
Blocked
37%
Avg conflicts / tx
1.43
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,140,630 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w07w18w29w312w413w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ed1f9d0…fc7f
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0x88b81e23…29b3
0x34b655…2a6f
8 touches
6 conflicts
0xbdf85442…6fce
0x34b655…2a6f
8 touches
6 conflicts
0x948836ff…59ab
0x34b655…2a6f
8 touches
6 conflicts
0xd584e803…93b2
0x34b655…2a6f
4 touches
2 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