← previous blocknext block →recent activity
Analyzing
Block #101,975,871
14 transactions · 14 stateful · 2026-09-04 18:49:29 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,975,871 · 14 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
1w02w13w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04d962b7…1cc0
0x34b655…2a6f
4 touches
1 conflict
0x63c8dcc7…3bdb
0x34b655…2a6f
4 touches
1 conflict
0x897879a1…9c78
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x8e33015d…b134
0x34b655…2a6f
4 touches
1 conflict
0x8feb2121…031a
0x34b655…2a6f
4 touches
1 conflict
0x9d7ac3b9…22f8
0x34b655…2a6f
4 touches
1 conflict
0xc52785b9…08f8
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
1 conflict on slot 0x04d962b719…b81cc0
Audit this contract →
← previous block·next block →recent activity