← previous blocknext block →recent activity
Analyzing
Block #101,669,669
21 transactions · 18 stateful · 2026-09-03 17:05:48 UTC
Parallelism
81/100
Blocked
44%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,669,669 · 21 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
1w02w13w24w35w06w19w110w215w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf339fa40…54c2
0x34b655…2a6f
8 touches
6 conflicts
0x230b0b56…a675
0x34b655…2a6f
6 touches
3 conflicts
0x29a58269…011a
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xeb4304a5…dd06
0x34b655…2a6f
6 touches
3 conflicts
0xecb7a41d…e6d3
0x34b655…2a6f
6 touches
3 conflicts
0x6be0d881…854e
0x34b655…2a6f
6 touches
3 conflicts
0x70d81211…f49f
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
6 conflicts on slot 0xf339fa40a0…0054c2
Audit this contract →
← previous block·next block →recent activity