← previous blocknext block →recent activity
Analyzing
Block #112,490,956
28 transactions · 24 stateful · 2026-10-11 14:20:45 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #112,490,956 · 28 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w09w116w018w119w220w321w422w423w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xccebf5c5…8758
0x34b655…2a6f
10 touches
10 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0x51af0e92…4020
0x34b655…2a6f
8 touches
6 conflicts
0x62aca140…f539
0x34b655…2a6f
8 touches
6 conflicts
0x3f5c1ed2…9bee
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6f6fc26c…3e34
0x34b655…2a6f
4 touches
1 conflict
0x85277a56…1d47
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: Perpl
10 conflicts on slot 0xccebf5c5cb…c88758
Audit this contract →
← previous block·next block →recent activity