← previous blocknext block →recent activity
Analyzing
Block #108,476,790
20 transactions · 19 stateful · 2026-09-27 13:26:26 UTC
Parallelism
85/100
Blocked
37%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,476,790 · 20 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
3w04w18w09w110w012w113w014w116w217w018w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x08cfec9d…7ef0
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c6
0x508254…98bd
4 touches
1 conflict
0x4ea2b33b…7dbc
0x508254…98bd
4 touches
1 conflict
0xe22c1d6f…b5c7
0x508254…98bd
4 touches
1 conflict
0x8ffa3328…ce11
0xe52b14…7230
4 touches
1 conflict
0x892daf6e…48d8
0x065c9d…c394
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