← previous blocknext block →recent activity
Analyzing
Block #107,806,112
17 transactions · 13 stateful · 2026-09-25 05:10:59 UTC
Parallelism
88/100
Blocked
8%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #107,806,112 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
13w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a663e9a…a9cb
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c4
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c5
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c7
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c8
0x508254…98bd
4 touches
1 conflict
0x0dd3bdfb…7537
0x34b655…2a6f
2 touches
0 conflicts
0x0dd3bdfb…7538
0x34b655…2a6f
2 touches
0 conflicts
0x2130a548…c1de
0x34b655…2a6f
2 touches
0 conflicts
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: 0x508254c8…4a98bd
1 conflict on slot 0x3a663e9a3a…2fa9cb
Audit this contract →
← previous block·next block →recent activity