← previous blocknext block →recent activity
Analyzing
Block #101,966,059
25 transactions · 24 stateful · 2026-09-04 17:59:48 UTC
Parallelism
92/100
Blocked
13%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,966,059 · 25 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w010w011w115w117w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xddd20e39…d524
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x31519d10…f76b
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x8b9390da…3820
0x34b655…2a6f
4 touches
1 conflict
0x0eb2f8c6…fcb7
0x34b655…2a6f
2 touches
0 conflicts
0x16a8cd0c…27bd
0x34b655…2a6f
2 touches
0 conflicts
0x366a19b0…f065
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
1 conflict on slot 0xddd20e3989…a2d524
Audit this contract →
← previous block·next block →recent activity