← previous blocknext block →recent activity
Analyzing
Block #106,281,881
16 transactions · 16 stateful · 2026-09-19 21:15:45 UTC
Parallelism
69/100
Blocked
56%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,281,881 · 16 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
1w02w14w07w18w09w210w311w412w313w414w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ba10aad…9bc5
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x418e9dd6…5263
0x34b655…2a6f
6 touches
3 conflicts
0xce661c37…0f0c
0x34b655…2a6f
6 touches
3 conflicts
0x5b6af007…0f35
0x34b655…2a6f
4 touches
1 conflict
0x6a66efe7…4bd7
0x34b655…2a6f
4 touches
1 conflict
0x8ce695ab…a7c8
0x34b655…2a6f
4 touches
1 conflict
0xfe2577ac…677b
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
6 conflicts on slot 0x9ba10aada6…3c9bc5
Audit this contract →
← previous block·next block →recent activity