← previous blocknext block →recent activity
Analyzing
Block #112,588,666
18 transactions · 17 stateful · 2026-10-11 22:32:22 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,588,666 · 18 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
1w02w110w011w112w013w114w215w316w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b458e47…5ab5
0x34b655…2a6f
8 touches
6 conflicts
0x15edc744…42d3
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0040
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0057
0x1b6862…e19c
4 touches
1 conflict
0x21d8e673…067f
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 0x1b458e4770…d25ab5
Audit this contract →
← previous block·next block →recent activity