← previous blocknext block →recent activity
Analyzing
Block #112,583,565
19 transactions · 18 stateful · 2026-10-11 22:06:43 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,583,565 · 19 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
1w02w15w010w111w012w113w114w215w318w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23521e1f…510b
0x34b655…2a6f
6 touches
3 conflicts
0xab2a87f1…eb01
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x68cb7ddc…4c9b
0xd32edf…ff58
5 touches
3 conflicts
0x143553f0…0670
0x1b6862…e19c
4 touches
1 conflict
0xbc08634c…2d88
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
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
3 conflicts on slot 0x23521e1f9d…73510b
Audit this contract →
← previous block·next block →recent activity