← previous blocknext block →recent activity
Analyzing
Block #106,569,956
18 transactions · 17 stateful · 2026-09-20 21:25:35 UTC
Parallelism
72/100
Blocked
35%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,569,956 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w010w111w212w313w416w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a7380bc…fe8c
0x34b655…2a6f
10 touches
10 conflicts
0x5e2ea201…12de
0x34b655…2a6f
4 touches
1 conflict
0xa6464996…3af9
0x34b655…2a6f
4 touches
1 conflict
0xa6c1a40f…67f1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe22ab637…7a8e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
10 conflicts on slot 0x8a7380bcee…eefe8c
Audit this contract →
← previous block·next block →recent activity