← previous blocknext block →recent activity
Analyzing
Block #112,528,327
28 transactions · 25 stateful · 2026-10-11 17:28:48 UTC
Parallelism
43/100
Blocked
64%
Avg conflicts / tx
4.57
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #112,528,327 · 28 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w410w511w612w713w816w821w922w1023w1124w1225w1326w1427w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d9ef283…ddd1
0x34b655…2a6f
32 touches
120 conflicts
0xb37353f0…fd10
0x34b655…2a6f
20 touches
45 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
18 touches
36 conflicts
0xdd9dc4b3…73b8
0x34b655…2a6f
18 touches
36 conflicts
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
16 touches
28 conflicts
0x7a3d5e6f…7864
0x34b655…2a6f
16 touches
28 conflicts
0xa7d3cb90…e1d9
0x34b655…2a6f
16 touches
28 conflicts
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
120 conflicts on slot 0x7d9ef2836a…01ddd1
Audit this contract →
← previous block·next block →recent activity