← previous blocknext block →recent activity
Analyzing
Block #101,681,062
15 transactions · 14 stateful · 2026-09-03 18:03:06 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,681,062 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w06w07w18w19w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4fbd0a79…626a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x735a86cd…b64d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x0b3a121c…f803
0x34b655…2a6f
4 touches
1 conflict
0x2c6ea33d…18e2
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x70f836c8…cf6d
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
3 conflicts on slot 0x4fbd0a7965…4c626a
Audit this contract →
← previous block·next block →recent activity