← previous blocknext block →recent activity
Analyzing
Block #112,497,331
23 transactions · 21 stateful · 2026-10-11 14:52:50 UTC
Parallelism
78/100
Blocked
43%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,497,331 · 23 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
1w02w14w06w07w19w110w211w316w317w218w421w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc65f46dd…513c
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0040
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0055
0x1b6862…e19c
4 touches
1 conflict
0x451f51c7…d362
0x1b6862…e19c
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 0xc65f46dd9f…6d513c
Audit this contract →
← previous block·next block →recent activity