← previous blocknext block →recent activity
Analyzing
Block #101,020,384
23 transactions · 23 stateful · 2026-09-01 10:38:49 UTC
Parallelism
78/100
Blocked
52%
Avg conflicts / tx
1.22
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,020,384 · 23 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
1w02w03w04w15w16w07w18w29w213w114w217w318w319w421w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe45073e…6315
0x34b655…2a6f
8 touches
6 conflicts
0x71fad9ce…c11f
0x34b655…2a6f
8 touches
6 conflicts
0x9654e93b…e153
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x451e482b…7e7d
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 0xfe45073ed9…0c6315
Audit this contract →
← previous block·next block →recent activity