← previous blocknext block →recent activity
Analyzing
Block #107,278,391
27 transactions · 24 stateful · 2026-09-23 08:52:43 UTC
Parallelism
74/100
Blocked
63%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,278,391 · 27 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w18w09w110w011w112w214w215w316w118w119w420w521w223w326w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xdfa159d0…1576
0x065c9d…c394
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x050d7a8a…67d0
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x9f46242e…f550
0x34b655…2a6f
6 touches
3 conflicts
0x44d7acbf…e67e
0x1b6862…e19c
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