← previous blocknext block →recent activity
Analyzing
Block #112,484,510
14 transactions · 14 stateful · 2026-10-11 13:48:20 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #112,484,510 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w17w18w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x513f7af5…c728
0x34b655…2a6f
4 touches
1 conflict
0xefc629e7…776d
0xa6afd3…d132
4 touches
1 conflict
0xdb40334f…e0bc
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x763058f6…1dba
0xd32edf…ff58
3 touches
1 conflict
0x4fc88f62…4ff4
0xa6afd3…d132
3 touches
1 conflict
0xcaf54545…9b74
0xa6afd3…d132
3 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
1 conflict on slot 0x513f7af5d0…5ac728
Audit this contract →
← previous block·next block →recent activity