← previous blocknext block →recent activity
Analyzing
Block #112,386,964
14 transactions · 10 stateful · 2026-10-11 05:37:32 UTC
Parallelism
71/100
Blocked
30%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,386,964 · 14 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
7w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbce62604…ff5c
0x34b655…2a6f
8 touches
6 conflicts
0x9fb6a4d0…9a9e
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x0d69b170…f45b
0x34b655…2a6f
4 touches
1 conflict
0x0667a366…00ce
0x34b655…2a6f
4 touches
1 conflict
0x27daa6a5…11a4
0x34b655…2a6f
4 touches
1 conflict
0x307d2b06…f822
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 0xbce6260416…5bff5c
Audit this contract →
← previous block·next block →recent activity