← previous blocknext block →recent activity
Analyzing
Block #108,299,681
25 transactions · 22 stateful · 2026-09-26 22:35:06 UTC
Parallelism
80/100
Blocked
45%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,299,681 · 25 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
3w04w15w07w18w211w212w213w314w418w019w122w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42489693…763f
0x065c9d…c394
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xf5dc501b…831c
0x34b655…2a6f
6 touches
3 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
6 touches
3 conflicts
0x8da4c229…0f5e
0x34b655…2a6f
4 touches
1 conflict
0xb066c72c…87d2
0x34b655…2a6f
4 touches
1 conflict
0xc856ff11…2b9c
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 0x42489693c3…2a763f
Audit this contract →
← previous block·next block →recent activity