← previous blocknext block →recent activity
Analyzing
Block #101,842,105
14 transactions · 14 stateful · 2026-09-04 07:33:07 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,842,105 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w26w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xacf0d67f…184d
0x34b655…2a6f
6 touches
3 conflicts
0xd459a2b8…1ebc
0x34b655…2a6f
6 touches
3 conflicts
0xfe4336ac…92d0
0x34b655…2a6f
6 touches
3 conflicts
0x30e6c268…95b7
0x34b655…2a6f
4 touches
1 conflict
0x42f8c032…8268
0x34b655…2a6f
4 touches
1 conflict
0x45052c15…ce85
0x34b655…2a6f
4 touches
1 conflict
0x5352e591…0e63
0x34b655…2a6f
4 touches
1 conflict
0x53e08444…d671
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 0xacf0d67ffd…cb184d
Audit this contract →
← previous block·next block →recent activity