← previous blocknext block →recent activity
Analyzing
Block #106,199,872
18 transactions · 16 stateful · 2026-09-19 14:22:56 UTC
Parallelism
72/100
Blocked
50%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,199,872 · 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
1w02w04w16w18w212w013w114w315w416w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x95523e2a…4c01
0x065c9d…c394
6 touches
3 conflicts
0xe26c4e53…94c3
0x34b655…2a6f
4 touches
1 conflict
0xc7f6eab9…9e9f
0x34b655…2a6f
4 touches
1 conflict
0xcfe180d7…b5a4
0x34b655…2a6f
4 touches
1 conflict
0xd0abbfc1…77f1
0x34b655…2a6f
4 touches
1 conflict
0xe26c4e53…94c2
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity