← previous blocknext block →recent activity
Analyzing
Block #112,478,691
20 transactions · 19 stateful · 2026-10-11 13:19:03 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #112,478,691 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w07w19w211w213w115w316w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x732d4b2d…2590
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x53057a6c…ce62
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00b872aa…2957
0x34b655…2a6f
4 touches
1 conflict
0x3e23438e…1baa
0x34b655…2a6f
4 touches
1 conflict
0x716b6cca…df06
0x34b655…2a6f
4 touches
1 conflict
0xb1e59a4a…879b
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 0x732d4b2d9f…fd2590
Audit this contract →
← previous block·next block →recent activity