← previous blocknext block →recent activity
Analyzing
Block #101,992,607
21 transactions · 19 stateful · 2026-09-04 20:14:28 UTC
Parallelism
81/100
Blocked
37%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,992,607 · 21 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
2w03w16w012w013w115w216w017w318w319w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65903ef9…2567
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xaf199a64…16ed
0x34b655…2a6f
6 touches
3 conflicts
0x045532dd…4b7d
0x34b655…2a6f
6 touches
3 conflicts
0x356cb7cc…d9e7
0x34b655…2a6f
4 touches
1 conflict
0x357fb47a…f9e0
0x34b655…2a6f
4 touches
1 conflict
0x3b25d07f…1dee
0x34b655…2a6f
4 touches
1 conflict
0x4e188c04…31c4
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 0x65903ef9a0…7d2567
Audit this contract →
← previous block·next block →recent activity