← previous blocknext block →recent activity
Analyzing
Block #101,310,304
28 transactions · 23 stateful · 2026-09-02 10:57:43 UTC
Parallelism
86/100
Blocked
30%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,310,304 · 28 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
1w03w15w08w09w116w017w018w120w221w224w225w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
4 touches
1 conflict
0x00091bbf…a4de
0x34b655…2a6f
4 touches
1 conflict
0x0613e1a6…85cc
0x34b655…2a6f
4 touches
1 conflict
0x0e242955…7901
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x665ec3e9…f55c
0x34b655…2a6f
4 touches
1 conflict
0x7a6681a8…c81c
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 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity