← previous blocknext block →recent activity
Analyzing
Block #107,805,906
19 transactions · 19 stateful · 2026-09-25 05:09:57 UTC
Parallelism
74/100
Blocked
32%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,805,906 · 19 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
5w06w17w28w39w412w013w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0de7b2f…60c1
0x40c49f…2af0
10 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 conflicts
0x00e21a9f…3583
0x34b655…2a6f
4 touches
1 conflict
0x0f00dc03…2d53
0x34b655…2a6f
4 touches
1 conflict
0x21a99841…6d8d
0x34b655…2a6f
4 touches
1 conflict
0x3750b746…5a9e
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: 0x40c49f17…d22af0
10 conflicts on slot 0xf0de7b2f94…f960c1
Audit this contract →
← previous block·next block →recent activity