← previous blocknext block →recent activity
Analyzing
Block #101,667,027
15 transactions · 15 stateful · 2026-09-03 16:52:30 UTC
Parallelism
80/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,667,027 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w17w08w110w011w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7ed3b40c…55fb
0x8964d7…10f8
4 touches
1 conflict
0x47784819…7b09
0x8964d7…10f8
4 touches
1 conflict
0x7ed3b40c…55f4
0x8964d7…10f8
4 touches
1 conflict
0x7ed3b40c…55f5
0x8964d7…10f8
4 touches
1 conflict
0x7ed3b40c…55f8
0x8964d7…10f8
4 touches
1 conflict
0x7ed3b40c…55f9
0x8964d7…10f8
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity