← previous blocknext block →recent activity
Analyzing
Block #101,667,510
22 transactions · 21 stateful · 2026-09-03 16:54:56 UTC
Parallelism
77/100
Blocked
29%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,667,510 · 22 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
1w02w03w15w112w213w316w420w021w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x110a3804…f842
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x290abc80…f605
0x34b655…2a6f
4 touches
1 conflict
0x2f17174f…68b4
0x34b655…2a6f
4 touches
1 conflict
0x3ecb4624…f0fe
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x53f7214d…8ec6
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
3 conflicts on slot 0x110a380404…49f842
Audit this contract →
← previous block·next block →recent activity