← previous blocknext block →recent activity
Analyzing
Block #112,074,775
16 transactions · 14 stateful · 2026-10-10 03:26:55 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,074,775 · 16 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
1w04w111w012w113w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x822abf1b…c65d
0x508254…98bd
10 touches
10 conflicts
0x4ea2b33b…7dbc
0x508254…98bd
8 touches
6 conflicts
0x3a663e9a…a9c5
0x508254…98bd
8 touches
6 conflicts
0x3a663e9a…a9c6
0x508254…98bd
8 touches
6 conflicts
0xe1c4d8e8…ffa8
0x508254…98bd
6 touches
3 conflicts
0x6c04daad…1130
0x508254…98bd
6 touches
3 conflicts
0x3a663e9a…a9c9
0x508254…98bd
4 touches
1 conflict
0x46344427…7edc
0x508254…98bd
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: 0x508254c8…4a98bd
10 conflicts on slot 0x822abf1b79…5ec65d
Audit this contract →
← previous block·next block →recent activity