← previous blocknext block →recent activity
Analyzing
Block #101,838,051
15 transactions · 15 stateful · 2026-09-04 07:12:43 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,838,051 · 15 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
2w03w14w28w29w311w413w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23a320fb…cbd7
0x34b655…2a6f
6 touches
3 conflicts
0xd5d9eb9b…be67
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xfcd5e68f…2a12
0x34b655…2a6f
4 touches
1 conflict
0x34dad526…5f98
0x34b655…2a6f
4 touches
1 conflict
0x0203a60f…d0bd
0x34b655…2a6f
4 touches
1 conflict
0x68c3526f…6bb9
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 0x23a320fbfb…26cbd7
Audit this contract →
← previous block·next block →recent activity