← previous blocknext block →recent activity
Analyzing
Block #112,475,636
24 transactions · 19 stateful · 2026-10-11 13:03:41 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #112,475,636 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w08w111w214w116w317w420w522w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d48d65d…29dc
0x34b655…2a6f
8 touches
6 conflicts
0x53057a6c…ce62
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x25957369…c648
0x34b655…2a6f
6 touches
3 conflicts
0x2ef367d0…290e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x513f7af5…c728
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…aaff
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
6 conflicts on slot 0x4d48d65d0a…1429dc
Audit this contract →
← previous block·next block →recent activity