← previous blocknext block →recent activity
Analyzing
Block #101,816,955
19 transactions · 17 stateful · 2026-09-04 05:26:36 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
0.68
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,816,955 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w17w28w312w013w116w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xeedc3757…d58c
0x99c7a7…8bf0
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xed4030fc…78ec
0x34b655…2a6f
4 touches
1 conflict
0x25ccb625…335f
0x754704…b603
4 touches
1 conflict
0xb5c1d5f6…712d
0x754704…b603
4 touches
1 conflict
0xcabfddb7…542b
0x754704…b603
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity