← previous blocknext block →recent activity
Analyzing
Block #112,526,242
23 transactions · 20 stateful · 2026-10-11 17:18:18 UTC
Parallelism
83/100
Blocked
45%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,526,242 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w113w114w215w317w218w220w021w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3548f3c5…af8e
0x34b655…2a6f
6 touches
3 conflicts
0xccebf5c5…8758
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0x464a82ff…41de
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0040
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0056
0x1b6862…e19c
4 touches
1 conflict
0x4d8c9332…b597
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 0x3548f3c5ae…eeaf8e
Audit this contract →
← previous block·next block →recent activity