← previous blocknext block →recent activity
Analyzing
Block #106,810,432
33 transactions · 21 stateful · 2026-09-21 17:36:54 UTC
Parallelism
85/100
Blocked
33%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,810,432 · 33 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
4w016w019w120w226w127w228w329w432w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x77ed432f…fa04
0x065c9d…c394
8 touches
6 conflicts
0x6a9e408e…3721
0x34b655…2a6f
8 touches
6 conflicts
0x95523e2a…4c01
0x065c9d…c394
6 touches
3 conflicts
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x366a19b0…f065
0x34b655…2a6f
4 touches
1 conflict
0x545e527e…0eb0
0x34b655…2a6f
4 touches
1 conflict
0x75f928fc…0465
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity