← previous blocknext block →recent activity
Analyzing
Block #101,971,122
13 transactions · 12 stateful · 2026-09-04 18:25:25 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,971,122 · 13 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
1w02w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bb0d58d…9dcf
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc3baa205…f26e
0x34b655…2a6f
4 touches
1 conflict
0xcd26fba5…21c6
0x34b655…2a6f
4 touches
1 conflict
0x37df7523…ccbb
0x754704…b603
4 touches
1 conflict
0xa6eca5ba…4390
0x754704…b603
4 touches
1 conflict
0xf96d61f8…8fd8
0x754704…b603
4 touches
1 conflict
0x6780777a…9fb1
0x99c7a7…8bf0
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 0x2bb0d58d61…679dcf
Audit this contract →
← previous block·next block →recent activity