← previous blocknext block →recent activity
Analyzing
Block #107,842,183
24 transactions · 22 stateful · 2026-09-25 08:12:32 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,842,183 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w112w013w114w215w316w417w522w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b61cc1d…4f81
0x34b655…2a6f
8 touches
6 conflicts
0x3ff9db2e…22f6
0x34b655…2a6f
8 touches
6 conflicts
0x0db691ab…3ee3
0x34b655…2a6f
8 touches
6 conflicts
0x31fc8950…3c77
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xfee8db15…cd58
0x34b655…2a6f
4 touches
1 conflict
0x2328941c…84d3
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
6 conflicts on slot 0x0b61cc1db3…6d4f81
Audit this contract →
← previous block·next block →recent activity