← previous blocknext block →recent activity
Analyzing
Block #100,048,708
20 transactions · 16 stateful · 2026-08-29 01:05:34 UTC
Parallelism
70/100
Blocked
31%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,048,708 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w08w011w112w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x206f4379…e08a
0x34b655…2a6f
8 touches
6 conflicts
0x6119ad89…63fe
0x34b655…2a6f
7 touches
6 conflicts
0xd2a76d80…ee44
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x9cf9008a…d826
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
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 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity