← previous blocknext block →recent activity
Analyzing
Block #101,661,156
29 transactions · 27 stateful · 2026-09-03 16:22:58 UTC
Parallelism
86/100
Blocked
33%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,661,156 · 29 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
2w03w14w25w07w18w210w113w014w115w216w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2130a548…c1de
0x34b655…2a6f
6 touches
3 conflicts
0x71e75883…77be
0x34b655…2a6f
6 touches
3 conflicts
0xba149d38…48fe
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x67c1f465…38b3
0x34b655…2a6f
4 touches
1 conflict
0x68844359…a80d
0x34b655…2a6f
4 touches
1 conflict
0xf1eadfaf…34e5
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
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 0x2130a548b9…31c1de
Audit this contract →
← previous block·next block →recent activity