← previous blocknext block →recent activity
Analyzing
Block #112,612,525
24 transactions · 23 stateful · 2026-10-12 00:32:25 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,612,525 · 24 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
1w06w07w08w19w010w111w114w216w319w020w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3744dbb…dece
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x77762137…2893
0x34b655…2a6f
4 touches
1 conflict
0xb9868b52…c77f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xce307d4a…b8d8
0x34b655…2a6f
4 touches
1 conflict
0x4635fb46…4cfd
0x34b655…2a6f
4 touches
1 conflict
0xe7cf1020…ad8c
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 0xe3744dbbea…1bdece
Audit this contract →
← previous block·next block →recent activity