← previous blocknext block →recent activity
Analyzing
Block #101,016,972
17 transactions · 14 stateful · 2026-09-01 10:21:39 UTC
Parallelism
76/100
Blocked
21%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,016,972 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w010w011w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd7f5b55…4994
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x93f1d5e2…9290
0x34b655…2a6f
4 touches
1 conflict
0xaa1efc75…f3d9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x18195fec…2bb3
0x34b655…2a6f
2 touches
0 conflicts
0x1b656d9e…20f2
0x34b655…2a6f
2 touches
0 conflicts
0x51087f5a…61f7
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0xfd7f5b557f…f74994
Audit this contract →
← previous block·next block →recent activity