← previous blocknext block →recent activity
Analyzing
Block #101,660,136
18 transactions · 18 stateful · 2026-09-03 16:17:50 UTC
Parallelism
72/100
Blocked
39%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,660,136 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w08w19w212w313w416w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3277870…f03e
0x34b655…2a6f
8 touches
6 conflicts
0x8d175439…fb79
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x23b2399c…6e4b
0x34b655…2a6f
6 touches
3 conflicts
0x69defb71…7b7e
0x34b655…2a6f
4 touches
1 conflict
0x70d81211…f49f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
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
6 conflicts on slot 0xa327787048…81f03e
Audit this contract →
← previous block·next block →recent activity