← previous blocknext block →recent activity
Analyzing
Block #105,869,496
37 transactions · 34 stateful · 2026-09-18 10:39:11 UTC
Parallelism
73/100
Blocked
65%
Avg conflicts / tx
1.73
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,869,496 · 37 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w28w39w410w512w018w133w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6caf33e2…c261
0x34b655…2a6f
14 touches
21 conflicts
0xd17580f9…ece1
0x754704…b603
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x279bb3e1…5a77
0x34b655…2a6f
8 touches
6 conflicts
0x41dd6ee3…0037
0x34b655…2a6f
8 touches
6 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
8 touches
6 conflicts
0x5fad6fee…7714
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0x6caf33e26f…3dc261
Audit this contract →
← previous block·next block →recent activity