← previous blocknext block →recent activity
Analyzing
Block #101,681,409
20 transactions · 15 stateful · 2026-09-03 18:04:51 UTC
Parallelism
80/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,681,409 · 20 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
3w04w19w210w315w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe67b4adf…4cc7
0x34b655…2a6f
6 touches
3 conflicts
0x1513b999…b52e
0x34b655…2a6f
4 touches
1 conflict
0x21a4d924…f40c
0x34b655…2a6f
4 touches
1 conflict
0x29a58269…011a
0x34b655…2a6f
4 touches
1 conflict
0x4f3cc09a…2804
0x34b655…2a6f
4 touches
1 conflict
0x5147806f…22f1
0x34b655…2a6f
4 touches
1 conflict
0x582cac9c…2571
0x34b655…2a6f
4 touches
1 conflict
0x60f8746d…b3d9
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 0xe67b4adf5e…4a4cc7
Audit this contract →
← previous block·next block →recent activity