← previous blocknext block →recent activity
Analyzing
Block #112,577,895
13 transactions · 13 stateful · 2026-10-11 21:38:11 UTC
Parallelism
62/100
Blocked
54%
Avg conflicts / tx
1.23
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,577,895 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w49w010w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0a73ae2…2e95
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xed00498d…8bd5
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x3755e8d5…232c
0x34b655…2a6f
4 touches
1 conflict
0x97980100…f8c8
0x34b655…2a6f
4 touches
1 conflict
0x00f245ce…1e10
0x34b655…2a6f
4 touches
1 conflict
0x258fcaf5…2084
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
10 conflicts on slot 0xc0a73ae2a1…182e95
Audit this contract →
← previous block·next block →recent activity