← previous blocknext block →recent activity
Analyzing
Block #112,577,938
21 transactions · 19 stateful · 2026-10-11 21:38:24 UTC
Parallelism
76/100
Blocked
53%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,577,938 · 21 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
1w02w14w08w09w111w112w213w214w315w316w417w119w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xc0a73ae2…2e95
0x34b655…2a6f
6 touches
3 conflicts
0xccebf5c5…8758
0x34b655…2a6f
6 touches
3 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0040
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0057
0x1b6862…e19c
4 touches
1 conflict
0x03e975a9…7ce1
0x1b6862…e19c
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
3 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity