← previous blocknext block →recent activity
Analyzing
Block #101,852,935
14 transactions · 14 stateful · 2026-09-04 08:27:35 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.79
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,852,935 · 14 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
1w02w15w06w17w29w311w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9ddc38b…475d
0x34b655…2a6f
8 touches
6 conflicts
0xa801b5ef…5b54
0x34b655…2a6f
8 touches
6 conflicts
0xea154cbb…f280
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x3ecb4624…f0fe
0x34b655…2a6f
6 touches
3 conflicts
0x8ec95f2b…f4d7
0x34b655…2a6f
6 touches
3 conflicts
0xab981df1…2941
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 0xd9ddc38bf4…21475d
Audit this contract →
← previous block·next block →recent activity