← previous blocknext block →recent activity
Analyzing
Block #112,612,049
21 transactions · 21 stateful · 2026-10-12 00:30:01 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #112,612,049 · 21 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
1w02w17w08w111w012w113w214w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xccebf5c5…8758
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0040
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0058
0x1b6862…e19c
4 touches
1 conflict
0x874cb67f…26e1
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
15 conflicts on slot 0xccebf5c5cb…c88758
Audit this contract →
← previous block·next block →recent activity