← previous blocknext block →recent activity
Analyzing
Block #112,523,298
19 transactions · 19 stateful · 2026-10-11 17:03:29 UTC
Parallelism
63/100
Blocked
42%
Avg conflicts / tx
1.26
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #112,523,298 · 19 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
4w06w17w28w39w410w511w612w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xccec40b5…9e85
0x34b655…2a6f
6 touches
3 conflicts
0x4de0b2a2…784f
0xc8689a…ee79
4 touches
1 conflict
0xa884aefc…8332
0x34b655…2a6f
4 touches
1 conflict
0xaa48195d…ffee
0x34b655…2a6f
4 touches
1 conflict
0xab3154b8…dbac
0x34b655…2a6f
4 touches
1 conflict
0xd1e80b4f…8d99
0x34b655…2a6f
4 touches
1 conflict
0x235b6aa7…ec37
0x37db7f…ec7b
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
21 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity