← previous blocknext block →recent activity
Analyzing
Block #100,140,743
24 transactions · 22 stateful · 2026-08-29 08:49:04 UTC
Parallelism
71/100
Blocked
41%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,140,743 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w19w111w213w314w416w522w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeab71d04…e42a
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd895ee0b…d301
0x34b655…2a6f
6 touches
3 conflicts
0x5ed1f9d0…fc7f
0x34b655…2a6f
6 touches
3 conflicts
0x2d071de0…c86e
0x34b655…2a6f
4 touches
1 conflict
0x4e58deff…c5d0
0x34b655…2a6f
4 touches
1 conflict
0x800856f0…3ee8
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0xeab71d04cf…a6e42a
Audit this contract →
← previous block·next block →recent activity