← previous blocknext block →recent activity
Analyzing
Block #105,549,236
20 transactions · 18 stateful · 2026-09-17 07:45:48 UTC
Parallelism
70/100
Blocked
56%
Avg conflicts / tx
1.3
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,549,236 · 20 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
1w02w13w05w17w210w011w112w213w314w417w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
12 touches
15 conflicts
0xfd4e632c…e14c
0x34b655…2a6f
10 touches
10 conflicts
0x00dd64fd…fd1e
0x6f6493…b480
10 touches
10 conflicts
0x21224483…c24d
0x6f6493…b480
10 touches
10 conflicts
0x237a9661…cf70
0x6f6493…b480
10 touches
10 conflicts
0x248fcba6…d3fc
0x6f6493…b480
10 touches
10 conflicts
0x29b537f5…0045
0x6f6493…b480
10 touches
10 conflicts
0x3151b709…4128
0x6f6493…b480
10 touches
10 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
15 conflicts on slot 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity