← previous blocknext block →recent activity
Analyzing
Block #112,368,239
26 transactions · 23 stateful · 2026-10-11 04:03:20 UTC
Parallelism
88/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #112,368,239 · 26 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w010w111w212w013w215w116w220w122w023w124w225w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ea2b33b…7dbc
0x508254…98bd
6 touches
3 conflicts
0x6c04daad…1130
0x508254…98bd
6 touches
3 conflicts
0x822abf1b…c65d
0x508254…98bd
6 touches
3 conflicts
0x3a663e9a…a9c5
0x508254…98bd
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0x3a663e9a…a9c6
0x508254…98bd
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x65903ef9…2567
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: 0x508254c8…4a98bd
3 conflicts on slot 0x4ea2b33b1b…857dbc
Audit this contract →
← previous block·next block →recent activity