← previous blocknext block →recent activity
Analyzing
Block #105,539,723
34 transactions · 22 stateful · 2026-09-17 06:57:55 UTC
Parallelism
82/100
Blocked
41%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,539,723 · 34 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
1w04w16w07w016w218w319w121w222w328w431w032w433w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59dccbd8…2bf6
0x34b655…2a6f
10 touches
10 conflicts
0xd35bb5ac…3586
0x065c9d…c394
8 touches
6 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
6 touches
3 conflicts
0x085df2c1…305a
0x34b655…2a6f
6 touches
3 conflicts
0x33da0dfa…bac6
0x34b655…2a6f
6 touches
3 conflicts
0x3643741b…109c
0x34b655…2a6f
6 touches
3 conflicts
0x647a9286…61c1
0x34b655…2a6f
6 touches
3 conflicts
0x68292fe7…d918
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0x59dccbd857…c52bf6
Audit this contract →
← previous block·next block →recent activity