← previous blocknext block →recent activity
Analyzing
Block #101,986,035
18 transactions · 17 stateful · 2026-09-04 19:41:05 UTC
Parallelism
83/100
Blocked
24%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,986,035 · 18 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
2w03w04w15w013w114w216w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x33b7fbba…64de
0x34b655…2a6f
4 touches
1 conflict
0xdac8e13c…bc65
0x34b655…2a6f
4 touches
1 conflict
0x02372d42…1871
0x34b655…2a6f
4 touches
1 conflict
0xadc848ee…5cb2
0x34b655…2a6f
4 touches
1 conflict
0xc52785b9…08f8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity