← previous blocknext block →recent activity
Analyzing
Block #101,969,848
11 transactions · 11 stateful · 2026-09-04 18:19:00 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,969,848 · 11 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
1w03w18w29w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x3d408a46…8a53
0x34b655…2a6f
4 touches
1 conflict
0x25ec781a…dca9
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xe8a87c9b…4065
0x34b655…2a6f
4 touches
1 conflict
0xee8f2472…bdaa
0x34b655…2a6f
4 touches
1 conflict
0x3b506c77…06bb
0x34b655…2a6f
2 touches
0 conflicts
0x474b9623…8272
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity